browser_cookie_delete
A destructive tool on the Playwright MCP server.
This record as markdown: /tools/hanato238-playwright-mcp/browser-cookie-delete.md
What browser_cookie_delete does on Playwright
AI agents call browser_cookie_delete 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.
Why browser_cookie_delete is rated Critical
The tool name explicitly includes 'delete', which strongly implies it removes cookies irreversibly. Cookies may store session tokens, authentication data, or user preferences. Deleting them cannot be undone without re-setting them, placing this in the Destructive category.
From the tool's definition Tool name 'browser_cookie_delete' — 'delete' suffix indicates irreversible removal of cookie data
Attacks that exploit this kind of access
The rule that runs browser_cookie_delete safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Playwright, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For browser_cookie_delete, this is the rule to start with:
browser_cookie_delete 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, apply this rule, and every browser_cookie_delete call is checked against it from then on.
Questions about browser_cookie_delete
browser_cookie_delete is a destructive tool on the Playwright MCP server. 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.
Register the Playwright MCP server in PolicyLayer and add a rule for browser_cookie_delete: 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.
browser_cookie_delete 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_delete 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_delete. 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_delete is provided by the Playwright MCP server (hanato238/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