List downstream callees inferred from Prometheus traffic metrics.
AI agents call get_outbound_traffic to retrieve information from Mcp Deploy Intel without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries Prometheus metrics to retrieve information about outbound traffic patterns and downstream service dependencies. It is purely informational—it reads existing metrics data and returns results. There are no side effects, no data modification, no code execution, and no destructive or financial operations.
From the tool's definition Tool name 'get_outbound_traffic' and description 'List downstream callees inferred from Prometheus traffic metrics' indicate a query operation that retrieves and displays data without modification or side effects.
Attacks that exploit this kind of access
List downstream callees inferred from Prometheus traffic metrics. It is categorised as a Read tool in the Mcp Deploy Intel MCP Server, which means it retrieves data without modifying state.
Register the Mcp Deploy Intel MCP server in PolicyLayer and add a rule for get_outbound_traffic: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Mcp Deploy Intel. Nothing to install.
get_outbound_traffic is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_outbound_traffic rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for get_outbound_traffic. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
get_outbound_traffic is provided by the Mcp Deploy Intel MCP server (vellankikoti/mcp-deploy-intel). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →