cookie_delete

THE RISK

Critical Risk

Why cookie_delete needs a policy

Deleting cookies is irreversible within the session context. Clearing all cookies can destroy authentication tokens, session identifiers, and other state data across all sites, which cannot be undone. This qualifies as Destructive rather than Write because the action permanently removes data rather than modifying it reversibly.

From the tool's definition 'Delete cookies. Both empty = clear all.' — irreversibly removes cookie data; 'clear all' implies bulk destruction of session state

Risk signalsBulk/mass operation — affects multiple targets

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

POLICY

How to control cookie_delete

PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Camoufox, and nothing reaches the server without passing your rules. This is the rule we recommend for cookie_delete:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "cookie_delete"
  ]
}

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

Create a free account and register MCP Camoufox — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More MCP Camoufox tools

Destructive localstorage_clear Clear all localStorage. Destructive reset_profile Delete the persistent profile (~/.camoufox-mcp/profile) entirely. Destructive browser_close Close the browser. Cookies are preserved in the persistent profile (~/.camoufox-mcp/profil Destructive tab_close Close a tab by index (-1 = active), or by url_contains. Execute batch_actions Execute multiple actions in one call. Each action: {type, ref?, value?, text?, key?, url?} Execute browser_launch Launch Camoufox stealth browser and navigate to URL. Browser persists between calls. Execute evaluate Execute JavaScript in page context. Execute frame_evaluate Execute JavaScript inside a specific frame/iframe.

All 102 MCP Camoufox tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in MCP Camoufox → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about cookie_delete

What does the cookie_delete tool do? +

Delete cookies. Both empty = clear all. It is categorised as a Destructive tool in the MCP Camoufox 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 cookie_delete? +

Register the MCP Camoufox MCP server in PolicyLayer and add a rule for cookie_delete: 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 Camoufox. Nothing to install.

What risk level is cookie_delete? +

cookie_delete 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 cookie_delete? +

Yes. Add a rate_limit block to the cookie_delete 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 cookie_delete completely? +

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

cookie_delete is provided by the MCP Camoufox MCP server (robithyusuf/mcp-camoufox). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every MCP Camoufox tool call.

Start from MCP Camoufox, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →