Critical Risk →

browser_cookie_clear

browser_cookie_clear

How to control browser_cookie_clear ↓

What browser_cookie_clear does on Playwright

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

Critical Risk

Why browser_cookie_clear needs a policy

The name strongly implies clearing/deleting all cookies, which is an irreversible destructive action (bulk deletion of browser cookie state). In the context of sibling tools like browser_cookie_delete, browser_cookie_set, etc., 'clear' typically means wiping all cookies at once rather than a targeted delete. This could disrupt authentication sessions and stored state irreversibly.

From the tool's definition Tool name 'browser_cookie_clear' on a Playwright browser automation server; description is empty

Documented attack patterns abuse exactly the kind of access browser_cookie_clear gives an agent:

How to control browser_cookie_clear

PolicyLayer is an MCP gateway — it sits between your AI agents and Playwright, and nothing reaches the server without passing your rules. This is the rule we recommend for browser_cookie_clear:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "browser_cookie_clear"
  ]
}

browser_cookie_clear disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register Playwright — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about browser_cookie_clear

What does the browser_cookie_clear tool do? +

browser_cookie_clear. It is categorised as a Destructive tool in the Playwright 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 browser_cookie_clear? +

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. Nothing to install.

What risk level is browser_cookie_clear? +

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.

Can I rate-limit browser_cookie_clear? +

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.

How do I block browser_cookie_clear completely? +

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.

What MCP server provides browser_cookie_clear? +

browser_cookie_clear is provided by the Playwright MCP server (@playwright/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Playwright tool call.

Start from Playwright, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

68 Playwright tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.