browser_cookie_clear
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.
'Clear' in the context of cookies typically means deleting all cookies (or all cookies for a domain), which is irreversible data deletion. This could destroy session data, authentication tokens, and other stored state. Sibling tools like 'browser_cookie_delete' further support that 'clear' implies a bulk/complete removal operation, making it more severe than a single delete.
From the tool's definition Tool name 'browser_cookie_clear' strongly implies clearing/deleting all cookies, which is an irreversible destructive action. Description is empty, so classification is based on name alone.
Attacks that exploit this kind of access
browser_cookie_clear. 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 (naumana3services-maker/mcp). 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 →