List captured HTTP exchanges with optional filters. Returns paginated results.
AI agents call proxy_list_traffic to retrieve information from Proxy without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries previously captured network traffic data. It performs no side effects, creates no new data, executes no code, deletes nothing, and moves no money. While the underlying proxy can capture sensitive data (which poses privacy risks in deployment), the tool itself is a simple data retrieval operation.
From the tool's definition Tool name is 'proxy_list_traffic' and description states it 'List[s] captured HTTP exchanges with optional filters.
Documented attack patterns abuse exactly the kind of access proxy_list_traffic gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Proxy, and nothing reaches the server without passing your rules. This is the rule we recommend for proxy_list_traffic:
{
"version": "1",
"default": "deny",
"tools": {
"proxy_list_traffic": {}
}
}proxy_list_traffic is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List captured HTTP exchanges with optional filters. Returns paginated results. It is categorised as a Read tool in the Proxy MCP Server, which means it retrieves data without modifying state.
Register the Proxy MCP server in PolicyLayer and add a rule for proxy_list_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 Proxy. Nothing to install.
proxy_list_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 proxy_list_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 proxy_list_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.
proxy_list_traffic is provided by the Proxy MCP server (yfe404/proxy-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Proxy, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
89 Proxy tools catalogued and risk-classified — across an index of 43,000+ MCP servers.