clear_all_cookies

Clear all browser cookies. Returns: Success status of the clear operation

SERVERChrome Devtools SOURCEbenjaminr/chrome-devtools-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/benjaminr-chrome-devtools-mcp/clear-all-cookies.md

What clear_all_cookies does on Chrome Devtools

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

Why clear_all_cookies is rated Critical

This tool irreversibly deletes all browser cookies across all origins. Misuse by an AI agent could log the user out of all websites, destroy session tokens, and remove authentication state. The 'all' scope amplifies the blast radius significantly, making this high severity. The operation cannot be undone.

From the tool's definition 'Clear all browser cookies' - the word 'clear' combined with 'all cookies' indicates irreversible bulk deletion of authentication tokens, session data, and other stored cookies across all domains

Risk signalsBulk/mass operation — affects multiple targets

Questions about clear_all_cookies

What does the clear_all_cookies tool do? +

Clear all browser cookies. Returns: Success status of the clear operation. It is categorised as a Destructive tool in the Chrome Devtools 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_all_cookies? +

Register the Chrome Devtools MCP server in PolicyLayer and add a rule for clear_all_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 Chrome Devtools. Nothing to install.

What risk level is clear_all_cookies? +

clear_all_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_all_cookies? +

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

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

clear_all_cookies is provided by the Chrome Devtools MCP server (benjaminr/chrome-devtools-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Chrome Devtools, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Chrome Devtools's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.