browser_cookie_clear
A destructive tool on the Playwright MCP server.
This record as markdown: /tools/alialobidm-playwright-mcp/browser-cookie-clear.md
What browser_cookie_clear does on Playwright MCP
AI agents call browser_cookie_clear to permanently remove resources in Playwright MCP, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why browser_cookie_clear is rated Critical
Clearing cookies is an irreversible bulk deletion action. Unlike 'browser_cookie_delete' (which likely targets a specific cookie), 'clear' suggests wiping all cookies, potentially destroying session state, authentication tokens, and preferences across all domains — a destructive operation with high blast radius in an automated browser context.
From the tool's definition Tool name 'browser_cookie_clear' — 'clear' implies bulk removal of cookies, which is irreversible. Sibling tools include 'browser_cookie_delete', 'browser_cookie_get', 'browser_cookie_list', 'browser_cookie_set', providing context that this tool likely clears…
Attacks that exploit this kind of access
The rule that runs browser_cookie_clear safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Playwright MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For browser_cookie_clear, this is the rule to start with:
browser_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 Playwright MCP, apply this rule, and every browser_cookie_clear call is checked against it from then on.
Questions about browser_cookie_clear
browser_cookie_clear is a destructive tool on the Playwright MCP server. It is categorised as a Destructive tool in the Playwright MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Playwright MCP server in PolicyLayer and add a rule for browser_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 Playwright MCP. Nothing to install.
browser_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 browser_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 browser_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.
browser_cookie_clear is provided by the Playwright MCP server (alialobidm/playwright-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Playwright, and thousands of servers like it.
Across the catalogue