Toggle browser display mode between headless and headed. When encountering CAPTCHAs or issues requiring visual interaction, switch to headed mode (headless: false) to show the browser window. After resolving, switch back to headless mode (headless: true). When switching an existing single context...
AI agents invoke toggle_display to trigger actions in Camofox. 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.
This tool triggers an external browser operation that changes the runtime configuration of an anti-detection browser session. It modifies the browser's display state and potentially invalidates existing tabs (tabsInvalidated), which is an external operational effect beyond simple data read/write.
From the tool's definition Toggle browser display mode between headless and headed... switch to headed mode... switch back to headless mode... the response includes a vncUrl field — open this URL in a browser to see and interact with the browser GUI
Documented attack patterns abuse exactly the kind of access toggle_display 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 toggle_display:
{
"version": "1",
"default": "deny",
"tools": {
"toggle_display": {
"limits": [
{
"counter": "toggle_display_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}toggle_display 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.
Free to start. No card required.
Toggle browser display mode between headless and headed. When encountering CAPTCHAs or issues requiring visual interaction, switch to headed mode (headless: false) to show the browser window. After resolving, switch back to headless mode (headless: true). When switching an existing single context to virtual or headed mode, the response includes a vncUrl field — open this URL in a browser to see and interact with the browser GUI. Check tabsInvalidated in the response: when true, recreate tabs; when false, existing tracked tabs remain usable and the override applies to future contexts. It is categorised as a Execute tool in the Camofox MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Camofox MCP server in PolicyLayer and add a rule for toggle_display: 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.
toggle_display is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the toggle_display 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 toggle_display. 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.
toggle_display 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.