Get one exchange from a recorded session by seq or exchange ID.
AI agents call proxy_get_session_exchange 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 is classified as Read because it retrieves data without side effects. However, severity is high because a proxy-MITM server captures sensitive network traffic including credentials, authentication tokens, API keys, personal data, and business-critical communications. An agent with access to this tool can exfiltrate any previously intercepted exchange, which could expose secrets or confidential information.
From the tool's definition Tool retrieves recorded session data ('Get one exchange from a recorded session by seq or exchange ID'). It is a read operation that queries existing captured network traffic without modifying or deleting it.
Documented attack patterns abuse exactly the kind of access proxy_get_session_exchange 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_get_session_exchange:
{
"version": "1",
"default": "deny",
"tools": {
"proxy_get_session_exchange": {}
}
}proxy_get_session_exchange 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.
Get one exchange from a recorded session by seq or exchange ID. 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_get_session_exchange: 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_get_session_exchange 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_get_session_exchange 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_get_session_exchange. 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_get_session_exchange 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.