Launch Camoufox stealth browser and navigate to URL. Browser persists between calls.
AI agents invoke browser_launch to trigger actions in MCP Camoufox. 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.
browser_launch initiates a persistent browser instance capable of visiting any URL and performing subsequent automated actions (as evidenced by sibling tools like batch_actions, auth_capture, and the stated scraping/form-filling capabilities).
From the tool's definition Tool "launches" a browser and "navigates to URL", enabling arbitrary web automation and interaction. The server description emphasizes "full browser control for tasks like form filling, data scraping, and session management" and explicitly mentions "bypassing…
Documented attack patterns abuse exactly the kind of access browser_launch gives an agent:
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 browser_launch:
{
"version": "1",
"default": "deny",
"tools": {
"browser_launch": {
"limits": [
{
"counter": "browser_launch_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}browser_launch 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.
Launch Camoufox stealth browser and navigate to URL. Browser persists between calls. It is categorised as a Execute tool in the MCP Camoufox MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MCP Camoufox MCP server in PolicyLayer and add a rule for browser_launch: 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.
browser_launch 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 browser_launch 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 browser_launch. 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.
browser_launch 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.
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.