Scroll at the given coordinates in the specified direction.
AI agents invoke computer_scroll to trigger actions in Computer Use MCP Server. 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.
Scrolling is a browser/desktop action that interacts with the live X11 desktop environment. It can trigger side effects depending on what UI element is under the cursor (e.g., scrolling through a list, changing a value in a spinner, navigating a page).
From the tool's definition Scroll at the given coordinates in the specified direction — triggers a physical UI interaction (scroll event) on the desktop
Attacks that exploit this kind of access
Scroll at the given coordinates in the specified direction. It is categorised as a Execute tool in the Computer Use MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Computer Use MCP Server MCP server in PolicyLayer and add a rule for computer_scroll: 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 Computer Use MCP Server. Nothing to install.
computer_scroll 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 computer_scroll 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 computer_scroll. 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.
computer_scroll is provided by the Computer Use MCP Server MCP server (sebastianbaltes/claude_code_computer_use_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →