Scroll at the given screen coordinates. Pass verify_app to confirm the right app is frontmost first.
AI agents invoke scroll to trigger actions in Mcp Desktop. 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 an active UI control action that sends input events to the frontmost application. While scrolling itself doesn't create or delete data, it executes a UI operation that can trigger side effects depending on the target application (e.g., loading new content, activating UI elements). It falls under Execute as it performs an external operation whose effects depend on arguments (coordinates and target app).
From the tool's definition "Scroll at the given screen coordinates" — triggers a UI interaction (scroll event) at specified coordinates on the desktop
Attacks that exploit this kind of access
Scroll at the given screen coordinates. Pass verify_app to confirm the right app is frontmost first. It is categorised as a Execute tool in the Mcp Desktop MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mcp Desktop MCP server in PolicyLayer and add a rule for 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 Mcp Desktop. Nothing to install.
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 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 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.
scroll is provided by the Mcp Desktop MCP server (mocha06/mcp-desktop). 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 →