Close a browser tab and release resources. Always close tabs when done to free memory.
AI agents use close_tab to create or update resources in Camofox — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Camofox environment.
An AI agent can call close_tab faster than any human can review — one bad instruction and it creates or modifies resources in Camofox by the hundred, each call as confident as the last.
Documented attack patterns abuse exactly the kind of access close_tab gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Camofox, and nothing reaches the server without passing your rules. This is the rule we recommend for close_tab:
{
"version": "1",
"default": "deny",
"tools": {
"close_tab": {
"limits": [
{
"counter": "close_tab_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}close_tab stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Close a browser tab and release resources. Always close tabs when done to free memory. It is categorised as a Write tool in the Camofox MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Camofox MCP server in PolicyLayer and add a rule for close_tab: 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 Camofox. Nothing to install.
close_tab is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the close_tab 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.
Set action: deny in the PolicyLayer policy for close_tab. 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.
close_tab is provided by the Camofox MCP server (redf0x1/camofox-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 47 Camofox tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
47 Camofox tools catalogued and risk-classified — across an index of 42,500+ MCP servers.