Critical Risk →

tab_close

Close a tab by index (-1 = active), or by url_contains.

How to control tab_close ↓

What tab_close does on MCP Camoufox

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

Critical Risk

Why tab_close needs a policy

Closing a browser tab is an irreversible action that terminates that tab's session, losing any unsaved state, form data, or in-progress operations associated with it. It cannot be undone once executed. The blast radius is medium — it could disrupt automation workflows or lose session state, but is limited in scope to a single browser tab.

From the tool's definition Close a tab by index (-1 = active), or by url_contains

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

How to control tab_close

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

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

tab_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 MCP Camoufox — 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 tab_close

What does the tab_close tool do? +

Close a tab by index (-1 = active), or by url_contains. It is categorised as a Destructive tool in the MCP Camoufox 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 tab_close? +

Register the MCP Camoufox MCP server in PolicyLayer and add a rule for tab_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 MCP Camoufox. Nothing to install.

What risk level is tab_close? +

tab_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 tab_close? +

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

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

tab_close is provided by the MCP Camoufox MCP server (robithyusuf/mcp-camoufox). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every MCP Camoufox tool call.

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

102 MCP Camoufox 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.