Critical Risk →

close_page

Closes the page by its index. The last open page cannot be closed.

How to control close_page ↓

What close_page does on ReverseCraft DevTools MCP

AI agents call close_page to permanently remove resources in ReverseCraft DevTools MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why close_page needs a policy

Closing a browser page is an irreversible action that destroys the current page state, any unsaved work, and active sessions. The page cannot be restored once closed, making this a destructive operation. Severity is medium because while it disrupts the current browser session, it doesn't affect persistent data outside the browser.

From the tool's definition Closes the page by its index

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

How to control close_page

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

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

close_page 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 ReverseCraft DevTools MCP — 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 close_page

What does the close_page tool do? +

Closes the page by its index. The last open page cannot be closed. It is categorised as a Destructive tool in the ReverseCraft DevTools 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 close_page? +

Register the ReverseCraft DevTools 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 ReverseCraft DevTools MCP. Nothing to install.

What risk level is close_page? +

close_page 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 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 ReverseCraft DevTools MCP server (reverse-craft/rc-devtools-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every ReverseCraft DevTools MCP tool call.

Start from ReverseCraft DevTools MCP, 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.

46 ReverseCraft DevTools MCP 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.