cookie_clear
Clear all cookies from the current browser session.
This record as markdown: /tools/mcp-anything/cookie-clear.md
What cookie_clear does on Mcp Anything
AI agents call cookie_clear 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.
Why cookie_clear is rated Critical
Clearing cookies is a destructive action that cannot be easily undone; it permanently removes browser session and authentication data. While not critical (no financial or code execution impact), it qualifies as Destructive because it erases data without recovery.
From the tool's definition Tool named 'cookie_clear' with description 'Clear all cookies from the current browser session' — this irreversibly deletes stored cookie data.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs cookie_clear 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_clear, this is the rule to start with:
cookie_clear is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Anything, apply this rule, and every cookie_clear call is checked against it from then on.
Questions about cookie_clear
Clear all cookies from the current browser session. 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.
Register the Mcp Anything MCP server in PolicyLayer and add a rule for cookie_clear: 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.
cookie_clear is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the cookie_clear 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.
Set action: deny in the PolicyLayer policy for cookie_clear. 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.
cookie_clear 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.
More on Mcp Anything, and thousands of servers like it.
Across the catalogue