Clear all cookies from the browser session.
AI agents call browser_clear_cookies to permanently remove resources in MCProxy — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Clearing all cookies permanently removes stored session data, authentication credentials, and state information from the browser session. This is an irreversible destructive action — once cookies are cleared, the data is gone and any active sessions are invalidated.
From the tool's definition 'Clear all cookies from the browser session' — clearing cookies is an irreversible deletion of session data (authentication tokens, preferences, session state) that cannot be undone within the current browser session.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Clear all cookies from the browser session. It is categorised as a Destructive tool in the MCProxy MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MCProxy MCP server in PolicyLayer and add a rule for browser_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 MCProxy. Nothing to install.
browser_clear_cookies 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 browser_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.
Set action: deny in the PolicyLayer policy for browser_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.
browser_clear_cookies is provided by the MCProxy MCP server (saladtechnologies/mcproxy). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →