browser_perform
Perform a task with the browser. It can click, type, export, capture screenshot, drag, hover, select options, etc.
This record as markdown: /tools/cowork-bench/browser-perform.md
What browser_perform does on Cowork Bench
AI agents invoke browser_perform to trigger actions in Cowork Bench. 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_perform is rated High
This tool executes browser actions (click, type, drag, hover, select, export) whose effects depend entirely on arguments. It can interact with any web interface, submit forms, trigger downloads, and perform arbitrary browser-mediated operations — spanning a wide range of potential side effects.
From the tool's definition Perform a task with the browser. It can click, type, export, capture screenshot, drag, hover, select options, etc.
Attacks that exploit this kind of access
The rule that runs browser_perform safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Cowork Bench, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For browser_perform, this is the rule to start with:
browser_perform 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 Bench, apply this rule, and every browser_perform call is checked against it from then on.
Questions about browser_perform
Perform a task with the browser. It can click, type, export, capture screenshot, drag, hover, select options, etc. It is categorised as a Execute tool in the Cowork Bench MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Cowork Bench MCP server in PolicyLayer and add a rule for browser_perform: 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 Bench. Nothing to install.
browser_perform 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_perform 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_perform. 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_perform is provided by the Cowork Bench MCP server (0717376/cowork_bench). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Cowork Bench, and thousands of servers like it.
Across the catalogue