close_page · MCP Playwright Server MCP: Risk & Policy

WHAT IT DOES

What close_page does on MCP Playwright Server

AI agents invoke close_page to trigger actions in MCP Playwright Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why close_page needs a policy

Closing a page is a browser action that triggers an external operation (destroying a browser page context). While it doesn't delete persistent data, it is an irreversible action within the session that could cause loss of unsaved state or disrupt ongoing automation workflows. It falls under Execute as it controls external browser behavior rather than reading or writing data.

From the tool's definition Close a page — terminates an active browser page/tab, which is an external browser operation with side effects

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

close_page Rate-limited

close_page stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "close_page": {
      "limits": [
        {
          "counter": "close_page_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches MCP Playwright Server, so you can run agents against it safely.

FAQ

Questions about close_page

What does the close_page tool do? +

Close a page. It is categorised as a Execute tool in the MCP Playwright Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on close_page? +

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

What risk level is close_page? +

close_page is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit close_page? +

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

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

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