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).

SERVERCoWork OS SOURCECoWork-OS/CoWork-OS
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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".

Questions about browser_act_batch

What does the browser_act_batch tool do? +

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.

How do I enforce a policy on browser_act_batch? +

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.

What risk level is browser_act_batch? +

browser_act_batch is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit browser_act_batch? +

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.

How do I block browser_act_batch completely? +

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.

What MCP server provides browser_act_batch? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of CoWork OS's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.