Launch cloakbrowser (stealth Chromium) with proxy flags and SPKI certificate trust. Built-in source-level fingerprint patches + humanize mode. Driven via Playwright — locator-based tools replace CDP.
AI agents invoke interceptor_browser_launch to trigger actions in Proxy. 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.
The tool explicitly launches a Chromium browser instance with specific flags and capabilities, then drives it via Playwright for automated browser automation. This is an Execute category risk because it triggers external process execution (browser launch) whose effects depend on subsequent arguments and actions.
From the tool's definition Launch cloakbrowser (stealth Chromium) with proxy flags... Driven via Playwright — locator-based tools replace CDP. This launches and controls a browser instance, which constitutes code/process execution.
Documented attack patterns abuse exactly the kind of access interceptor_browser_launch gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Proxy, and nothing reaches the server without passing your rules. This is the rule we recommend for interceptor_browser_launch:
{
"version": "1",
"default": "deny",
"tools": {
"interceptor_browser_launch": {
"limits": [
{
"counter": "interceptor_browser_launch_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}interceptor_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 cloakbrowser (stealth Chromium) with proxy flags and SPKI certificate trust. Built-in source-level fingerprint patches + humanize mode. Driven via Playwright — locator-based tools replace CDP. It is categorised as a Execute tool in the Proxy MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Proxy MCP server in PolicyLayer and add a rule for interceptor_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 Proxy. Nothing to install.
interceptor_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 interceptor_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 interceptor_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.
interceptor_browser_launch is provided by the Proxy MCP server (yfe404/proxy-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Proxy, 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.
89 Proxy tools catalogued and risk-classified — across an index of 43,000+ MCP servers.