New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

browser_scroll_to_bottom

Scroll to the bottom of the page

SERVERCowork Bench SOURCE0717376/cowork_bench
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-bench/browser-scroll-to-bottom.md

What browser_scroll_to_bottom does on Cowork Bench

AI agents invoke browser_scroll_to_bottom 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_to_bottom is rated High

Scrolling a browser page is a browser action/interaction. It does not read data, write/modify persistent data, or delete anything, but it does execute a UI-level operation in a live browser environment. Misuse potential is low since it only changes the viewport position.

From the tool's definition 'Scroll to the bottom of the page' — triggers a browser action (scrolling) that constitutes an external operation within a browser context

Questions about browser_scroll_to_bottom

What does the browser_scroll_to_bottom tool do? +

Scroll to the bottom of the page. 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.

How do I enforce a policy on browser_scroll_to_bottom? +

Register the Cowork Bench MCP server in PolicyLayer and add a rule for browser_scroll_to_bottom: 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.

What risk level is browser_scroll_to_bottom? +

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

Can I rate-limit browser_scroll_to_bottom? +

Yes. Add a rate_limit block to the browser_scroll_to_bottom 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_scroll_to_bottom completely? +

Set action: deny in the PolicyLayer policy for browser_scroll_to_bottom. 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_scroll_to_bottom? +

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

// 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 Bench'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.