browser_scroll_up
Scroll the page up to see content above the current viewport
This record as markdown: /tools/cowork-bench/browser-scroll-up.md
What browser_scroll_up does on Cowork Bench
AI agents invoke browser_scroll_up 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_scroll_up is rated High
This tool triggers a browser action (scrolling) which is an external operation affecting the browser state. While it only changes the viewport position and has no data modification side effects, it is an Execute-category action as it performs a browser interaction rather than purely reading data.
From the tool's definition Scroll the page up to see content above the current viewport
Attacks that exploit this kind of access
The rule that runs browser_scroll_up 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_scroll_up, this is the rule to start with:
browser_scroll_up 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_scroll_up call is checked against it from then on.
Questions about browser_scroll_up
Scroll the page up to see content above the current viewport. 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_scroll_up: 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_scroll_up 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_scroll_up 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_scroll_up. 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_scroll_up 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