AI agents invoke browser_batch to trigger actions in Cdp Bridge. 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 description is empty, lowering confidence. However, given the server context (browser automation via Chromium plugin) and the 'batch' suffix, this tool likely executes multiple browser actions in sequence. Sibling tools include high-risk operations like JavaScript execution and navigation.
From the tool's definition Tool name 'browser_batch' on a server designed for browser automation; sibling tools include browser_execute_js, browser_navigate, browser_scan, browser_screenshot, etc.
Documented attack patterns abuse exactly the kind of access browser_batch gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Cdp Bridge, and nothing reaches the server without passing your rules. This is the rule we recommend for browser_batch:
{
"version": "1",
"default": "deny",
"tools": {
"browser_batch": {
"limits": [
{
"counter": "browser_batch_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}browser_batch 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.
browser_batch. It is categorised as a Execute tool in the Cdp Bridge MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Cdp Bridge MCP server in PolicyLayer and add a rule for browser_batch: 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 Cdp Bridge. Nothing to install.
browser_batch 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_batch 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_batch. 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_batch is provided by the Cdp Bridge MCP server (unagi-cq/cdp-bridge-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 9 Cdp Bridge tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
9 Cdp Bridge tools catalogued and risk-classified — across an index of 42,500+ MCP servers.