clear_cookies

Clears all browser cookies via CDP Network.clearBrowserCookies. Useful

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/clear-cookies.md

WHAT IT DOES

What clear_cookies does on Js Reverse

AI agents call clear_cookies 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 clear_cookies is rated Critical

Clearing all browser cookies is an irreversible destructive action — once cookies are deleted, session tokens, authentication state, and stored preferences are permanently lost and cannot be recovered by the tool itself. The blast radius is medium since it affects browser session state but is limited to the browser context.

From the tool's definition Clears all browser cookies via CDP Network.clearBrowserCookies

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs clear_cookies 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 clear_cookies, this is the rule to start with:

clear_cookies Hidden

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

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 clear_cookies call is checked against it from then on.

FAQ

Questions about clear_cookies

What does the clear_cookies tool do? +

Clears all browser cookies via CDP Network.clearBrowserCookies. Useful. 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 clear_cookies? +

Register the Js Reverse MCP server in PolicyLayer and add a rule for clear_cookies: 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 clear_cookies? +

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

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

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

clear_cookies 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

clear_project_index on ACE-MCP →clear_renders on Why Did You Render →knowledge_clear on Templonix Lite MCP Server →clear_scan on Frida Game Hacking MCP → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →