browser_act_batch
Execute a batch of browser actions in sequence. Use for multi-step interactions (e.g. fill form, click submit, wait for result).
This record as markdown: /tools/cowork-os/browser-act-batch.md
What browser_act_batch does on CoWork OS
AI agents invoke browser_act_batch to trigger actions in CoWork OS. 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.
Why browser_act_batch is rated High
This tool executes browser automation commands whose effects depend entirely on the arguments—it could be used to perform financial transactions, submit unauthorized forms, exfiltrate data, or interact with web applications in unintended ways.
From the tool's definition Tool description states "Execute a batch of browser actions in sequence" and mentions triggering interactions like "fill form, click submit, wait for result".
Attacks that exploit this kind of access
The rule that runs browser_act_batch safely
PolicyLayer is an MCP gateway: it sits between your AI agents and CoWork OS, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For browser_act_batch, this is the rule to start with:
browser_act_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.
The button opens the PolicyLayer dashboard: create your workspace, connect CoWork OS, apply this rule, and every browser_act_batch call is checked against it from then on.
Questions about browser_act_batch
Execute a batch of browser actions in sequence. Use for multi-step interactions (e.g. fill form, click submit, wait for result). It is categorised as a Execute tool in the CoWork OS MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the CoWork OS MCP server in PolicyLayer and add a rule for browser_act_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 CoWork OS. Nothing to install.
browser_act_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_act_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_act_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_act_batch is provided by the CoWork OS MCP server (CoWork-OS/CoWork-OS). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on CoWork OS, and thousands of servers like it.
Across the catalogue