Scroll at screen coordinates. dy negative=up, positive=down.
AI agents invoke mouse_scroll to trigger actions in GNOME Desktop 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.
mouse_scroll injects mouse scroll events into the desktop environment via D-Bus. This is an input injection/execution action that simulates physical user interaction, potentially scrolling through sensitive content, triggering UI actions, or interacting with application interfaces in unintended ways. It has side effects that depend on the current state of the desktop and active application.
From the tool's definition Scroll at screen coordinates. dy negative=up, positive=down.
Documented attack patterns abuse exactly the kind of access mouse_scroll gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and GNOME Desktop MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for mouse_scroll:
{
"version": "1",
"default": "deny",
"tools": {
"mouse_scroll": {
"limits": [
{
"counter": "mouse_scroll_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}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.
Free to start. No card required.
Scroll at screen coordinates. dy negative=up, positive=down. It is categorised as a Execute tool in the GNOME Desktop MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the GNOME Desktop 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 GNOME Desktop MCP. Nothing to install.
mouse_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 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.
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.
mouse_scroll is provided by the GNOME Desktop MCP server (sbuysse/gnome-desktop-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from GNOME Desktop MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
30 GNOME Desktop MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.