Critical Risk →

proxy_delete_session

Delete a recorded session from disk.

How to control proxy_delete_session ↓

What proxy_delete_session does on Proxy

AI agents call proxy_delete_session 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.

Critical Risk

Why proxy_delete_session needs a policy

Deleting a recorded session from disk is a destructive action that cannot be undone. While the blast radius is scoped to session data (not arbitrary system files), the operation is inherently permanent.

From the tool's definition Tool description states 'Delete a recorded session from disk' — this is an irreversible deletion operation that removes data.

Documented attack patterns abuse exactly the kind of access proxy_delete_session gives an agent:

How to control proxy_delete_session

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_delete_session:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "proxy_delete_session"
  ]
}

proxy_delete_session disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register Proxy — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about proxy_delete_session

What does the proxy_delete_session tool do? +

Delete a recorded session from disk. 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.

How do I enforce a policy on proxy_delete_session? +

Register the Proxy MCP server in PolicyLayer and add a rule for proxy_delete_session: 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.

What risk level is proxy_delete_session? +

proxy_delete_session is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit proxy_delete_session? +

Yes. Add a rate_limit block to the proxy_delete_session 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.

How do I block proxy_delete_session completely? +

Set action: deny in the PolicyLayer policy for proxy_delete_session. 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.

What MCP server provides proxy_delete_session? +

proxy_delete_session 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.

Enforce policy on every Proxy tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.