delete_cookie

Deletes cookies matching the given name (optionally scoped by url,

SERVERJs Reverse SOURCE1600822305/js-reverse-mcp

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/1600822305-js-reverse-mcp/delete-cookie.md

WHAT IT DOES

What delete_cookie does on Js Reverse

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

RISK

Why delete_cookie is rated Critical

The tool permanently deletes cookies, which cannot be undone. Misuse could destroy session tokens, authentication cookies, or other critical browser state, potentially disrupting active sessions or causing data loss.

From the tool's definition 'Deletes cookies matching the given name' — explicitly removes cookies, which is an irreversible deletion of browser session/authentication data

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs delete_cookie safely

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

delete_cookie Hidden

delete_cookie 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": [
    "delete_cookie"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about delete_cookie

What does the delete_cookie tool do? +

Deletes cookies matching the given name (optionally scoped by url,. It is categorised as a Destructive tool in the Js Reverse 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 delete_cookie? +

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

What risk level is delete_cookie? +

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

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

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

delete_cookie is provided by the Js Reverse MCP server (1600822305/js-reverse-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Js Reverse, and thousands of servers like it.

This server

All 93 Js Reverse 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 →