Scroll

Scrolls at coordinates [x, y], a UI element

SERVERWindows-MCP SOURCE13888285815/windows-mcp

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/13888285815-windows-mcp/scroll.md

WHAT IT DOES

What Scroll does on Windows-MCP

AI agents invoke Scroll to trigger actions in Windows-MCP. 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.

RISK

Why Scroll is rated High

Scrolling is a UI automation action that simulates user input on the Windows OS. While scrolling itself has limited direct harm, it can trigger side effects depending on what UI element is targeted (e.g., scrolling through menus, triggering lazy-loaded content, or interacting with sensitive UI). It falls under Execute as it triggers external operations (OS-level UI interaction) whose effects depend on arguments.

From the tool's definition 'Scrolls at coordinates [x, y], a UI element' — triggers a UI interaction (simulated user input) at specific screen coordinates

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs Scroll safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Windows-MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For Scroll, this is the rule to start with:

Scroll Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "Scroll": {
      "limits": [
        {
          "counter": "scroll_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Windows-MCP, apply this rule, and every Scroll call is checked against it from then on.

FAQ

Questions about Scroll

What does the Scroll tool do? +

Scrolls at coordinates [x, y], a UI element. It is categorised as a Execute tool in the Windows-MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on Scroll? +

Register the Windows 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 Windows-MCP. Nothing to install.

What risk level is Scroll? +

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

Can I rate-limit Scroll? +

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.

How do I block Scroll completely? +

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.

What MCP server provides Scroll? +

Scroll is provided by the Windows MCP server (13888285815/windows-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Windows, and thousands of servers like it.

This server

All 18 Windows tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →