Agent Connection Telemetry Policy
Policy Name |
Agent Connection Telemetry |
Summary |
Tracks the number of requests made to agent or MCP server instances |
Category |
A2A and MCP |
First Flex Gateway version available |
1.11.0 |
Returned Status Codes |
No return codes exist for this policy. |
Summary
The Agent Connection Telemetry policy tracks the number of requests and what source makes the request to agent or MCP server instance.
To track the source of the request, the policy uses a DataWeave expression to extract an identification value from a request header. By default, the policy extracts the X-AGENT-ID header. The X-AGENT-ID header contains the Mulesoft instance ID.
To track the requests, the policy uses the mulesoft_agent_connection_count(source, destination) metric. Where source is the identification value extracted from the request header and destination is the agent or MCP server instance ID. Use Anypoint Monitoring to view the metric.
If the policy can’t extract the identification header, the policy doesn’t block or track the request.
| The Agent Connection Telemetry policy is applied by default to all agent and MCP server instances created using Agent Fabric. |
Configure Policy Parameters
Managed Flex Gateway and Flex Gateway Connected Mode
When you apply the policy to your API instance from the UI, the following parameters are displayed:
| Element | Description |
|---|---|
Source Agent ID |
DataWeave expression to extract the source identification value from the request header. By default, the |