mouse_scroll · Windows MCP Server MCP: Risk & Policy

WHAT IT DOES

What mouse_scroll does on Windows MCP Server

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

WHY IT NEEDS A POLICY

Why mouse_scroll needs a policy

Scrolling the mouse wheel is an active UI interaction that can trigger JavaScript/UI events, navigate through sensitive content, or scroll to and expose different application states. It is not a pure read operation, as it causes a state change in the UI. On a Windows automation server controlling a live desktop, misuse could scroll through sensitive data or accidentally trigger UI actions tied to scroll events.

From the tool's definition 'Scroll the mouse wheel' — triggers a physical UI interaction on the Windows desktop, causing side effects such as scrolling through content, triggering scroll-event handlers, or navigating UI elements.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

mouse_scroll Rate-limited

mouse_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": {
    "mouse_scroll": {
      "limits": [
        {
          "counter": "mouse_scroll_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Windows MCP Server, so you can run agents against it safely.

FAQ

Questions about mouse_scroll

What does the mouse_scroll tool do? +

Scroll the mouse wheel. It is categorised as a Execute tool in the Windows MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on mouse_scroll? +

Register the Windows MCP Server MCP server in PolicyLayer and add a rule for mouse_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 Server. Nothing to install.

What risk level is mouse_scroll? +

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

Can I rate-limit mouse_scroll? +

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

Set action: deny in the PolicyLayer policy for mouse_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 mouse_scroll? +

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