Critical Risk →

playwright_close

Close the browser and release all resources

How to control playwright_close ↓

What playwright_close does on Playwright MCP Server

AI agents call playwright_close 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.

Critical Risk

Why playwright_close needs a policy

Closing the browser and releasing all resources is an irreversible action that destroys the current browser session, any unsaved state, open pages, and accumulated context. This cannot be undone, making it Destructive. Severity is medium because it terminates an active session and could disrupt ongoing workflows, but does not delete persistent data.

From the tool's definition 'Close the browser and release all resources' — irreversibly terminates the browser session and frees all associated resources

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

How to control playwright_close

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

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

playwright_close 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 MCP Server — 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 playwright_close

What does the playwright_close tool do? +

Close the browser and release all resources. 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 playwright_close? +

Register the Playwright MCP Server MCP server in PolicyLayer and add a rule for playwright_close: 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 playwright_close? +

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

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

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

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

Enforce policy on every Playwright MCP Server tool call.

Start from Playwright MCP Server, 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.

29 Playwright MCP Server 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.