cookie_delete

Delete a cookie by name.

SERVERMcp Anything SOURCEZaymadkid/mcp-anything

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/mcp-anything/cookie-delete.md

WHAT IT DOES

What cookie_delete does on Mcp Anything

AI agents call cookie_delete to permanently remove resources in Mcp Anything, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why cookie_delete is rated Critical

The tool explicitly deletes a cookie by name, which is an irreversible removal operation. While cookies are relatively low-impact data, deletion cannot be undone without re-creation. The blast radius is medium since deleting session/auth cookies could disrupt user sessions or authentication state.

From the tool's definition 'Delete a cookie by name' - the word 'delete' indicates irreversible removal of data

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs cookie_delete safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Anything, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For cookie_delete, this is the rule to start with:

cookie_delete Hidden

cookie_delete is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

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

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Anything, apply this rule, and every cookie_delete call is checked against it from then on.

FAQ

Questions about cookie_delete

What does the cookie_delete tool do? +

Delete a cookie by name. It is categorised as a Destructive tool in the Mcp Anything 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 Anything 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 Anything. 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 Anything MCP server (Zaymadkid/mcp-anything). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Mcp Anything, and thousands of servers like it.

This server

All 261 Mcp Anything tools → Critical-risk tools on this server →

Across the catalogue

sms_delete_message on Twilio SMS MCP Server →delete_snapshot on Why Did You Render →calendar_delete_event on Templonix Lite MCP Server →delete_addon_domain on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →