List upstream callers inferred from Prometheus traffic metrics.
AI agents call get_inbound_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 reads traffic metrics from Prometheus to infer and display upstream caller information. It has no side effects, does not modify data, execute commands, or trigger external operations. It is purely informational and fits the Read category (retrieves or queries data).
From the tool's definition Tool description states 'List upstream callers inferred from Prometheus traffic metrics' — a query operation that retrieves and retrieves data from Prometheus without modification or execution of external operations.
Attacks that exploit this kind of access
List upstream callers 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_inbound_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_inbound_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_inbound_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_inbound_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_inbound_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 →