clear_cookies

A destructive tool on the Playwright MCP server.

SERVERPlaywright MCP Server SOURCEalexrwilliam/playwright-mcp-server

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/alexrwilliam-playwright-mcp-server/clear-cookies.md

WHAT IT DOES

What clear_cookies does on Playwright MCP Server

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

RISK

Why clear_cookies is rated Critical

Based on the tool name, it likely clears/deletes browser cookies, which is an irreversible deletion of stored session/authentication data. Sibling tools like 'add_cookies' and 'clear_storage' support this interpretation — 'clear' operations on a Playwright server typically purge data that cannot be recovered within the session. Confidence is moderate due to empty description.

From the tool's definition Tool name 'clear_cookies' on a Playwright browser automation server; description is empty and uninformative.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs clear_cookies safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Playwright MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For clear_cookies, this is the rule to start with:

clear_cookies Hidden

clear_cookies is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "clear_cookies"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Playwright MCP Server, apply this rule, and every clear_cookies call is checked against it from then on.

FAQ

Questions about clear_cookies

What does the clear_cookies tool do? +

clear_cookies is a destructive tool on the Playwright MCP Server MCP server. It is categorised as a Destructive tool in the Playwright MCP Server 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 clear_cookies? +

Register the Playwright MCP Server MCP server in PolicyLayer and add a rule for clear_cookies: 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 Server. Nothing to install.

What risk level is clear_cookies? +

clear_cookies 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 clear_cookies? +

Yes. Add a rate_limit block to the clear_cookies 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 clear_cookies completely? +

Set action: deny in the PolicyLayer policy for clear_cookies. 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 clear_cookies? +

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

KEEP EXPLORING

More on Playwright MCP Server, and thousands of servers like it.

This server

All 67 Playwright MCP Server tools → Critical-risk tools on this server →

Across the catalogue

clear_renders on Why Did You Render →knowledge_clear on Templonix Lite MCP Server →clear_scan on Frida Game Hacking MCP →clear_spam_box on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →