browser_cookie_delete

A destructive tool on the Playwright MCP server.

SERVERPlaywright MCP SOURCEalialobidm/playwright-mcp
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/alialobidm-playwright-mcp/browser-cookie-delete.md

What browser_cookie_delete does on Playwright MCP

AI agents call browser_cookie_delete 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_delete is rated Critical

The 'delete' suffix indicates this tool removes cookies, which is an irreversible action (data is gone until recreated). Sibling tools like browser_cookie_set, browser_cookie_get, and browser_cookie_clear confirm this is part of a cookie management suite where delete means permanent removal. Misuse could disrupt sessions or authentication state.

From the tool's definition Tool name 'browser_cookie_delete' — 'delete' strongly implies irreversible removal of cookie data. Description is empty, so classification is based on name alone.

Questions about browser_cookie_delete

What does the browser_cookie_delete tool do? +

browser_cookie_delete 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.

How do I enforce a policy on browser_cookie_delete? +

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

What risk level is browser_cookie_delete? +

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.

Can I rate-limit browser_cookie_delete? +

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.

How do I block browser_cookie_delete completely? +

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.

What MCP server provides browser_cookie_delete? +

browser_cookie_delete 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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Playwright's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.