Stop persistent on-disk capture and finalize the active session.
AI agents call proxy_session_stop to permanently remove resources in Proxy — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Stopping and finalizing a session is likely irreversible — once the session is finalized, the active capture state is terminated and cannot be resumed. 'Finalize' implies a permanent end to the session, which could mean loss of any unsaved or in-progress capture data. This is closer to Destructive than Write because the action cannot be undone.
From the tool's definition Stop persistent on-disk capture and finalize the active session
Documented attack patterns abuse exactly the kind of access proxy_session_stop 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_session_stop:
{
"version": "1",
"default": "deny",
"hide": [
"proxy_session_stop"
]
} proxy_session_stop disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Stop persistent on-disk capture and finalize the active session. It is categorised as a Destructive tool in the Proxy MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Proxy MCP server in PolicyLayer and add a rule for proxy_session_stop: 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_session_stop is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the proxy_session_stop 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_session_stop. 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_session_stop 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.