AI agents invoke scroll to trigger actions in EZComputerCtrl 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.
Scrolling is a desktop GUI interaction that executes a mouse wheel action on a target control. It has side effects (can trigger lazy-loading, navigation, or other scroll-event-driven behaviors) and is part of a broader visual automation toolkit alongside click and type_text, placing it in the Execute category. Misuse could cause unintended navigation or content loading, giving it medium severity.
From the tool's definition 滚动鼠标滚轮 (scroll mouse wheel at specified control) — triggers a UI interaction/browser action on the desktop
Documented attack patterns abuse exactly the kind of access scroll gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and EZComputerCtrl MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for scroll:
{
"version": "1",
"default": "deny",
"tools": {
"scroll": {
"limits": [
{
"counter": "scroll_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}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.
在指定控件处滚动鼠标滚轮。. It is categorised as a Execute tool in the EZComputerCtrl MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the EZComputerCtrl 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 EZComputerCtrl MCP. 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 EZComputerCtrl MCP server (jucieovo/ezcomputerctrl-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from EZComputerCtrl 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.
6 EZComputerCtrl MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.