This is a good question, and I am happy to explain why you are seeing this agent.
Windows Server 2012 introduced us for Network Virtualization using the GRE protocol (NVGRE).
In order to leverage NVGRE, you would have to manage your hosts entirely with powershell, if you didn't have VMM in place.
When VMM is in place (and really should be in place, when using NVGRE), VMM act as the complete management layer, also for the NVGRE part. Since NVGRE basically is a
policy driven technology, VMM need to keep track of every IP address used with NVGRE. During deployment of virtual machines connected to a VM Network with NVGRE (often referred to as Customer Addresses), VMM is able to configure static IP addresses
on to these VMs, using the agent you are mentioning. This was introduced in VMM 2012 SP1, and is also present in the R2 Release.
So to summarize, it is a Hyper-V Switch Extension that is required on all Windows Server with Hyper-V to have DHCP to work correctly.
-kn