Scroll the VM display up or down. Use to navigate long pages, lists, or chat threads in the GUI.
AI agents invoke orgo_scroll to trigger actions in Orgo 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.
Scrolling is a browser/GUI action that produces side effects in a running virtual computer session. It doesn't read, write, or destroy data directly, but it executes an input event on a remote VM display. This falls under Execute (browser/GUI actions). Misuse could cause unintended navigation but blast radius is moderate.
From the tool's definition 'Scroll the VM display up or down' and 'navigate long pages, lists, or chat threads in the GUI' — triggers a physical GUI interaction on a virtual machine display
Documented attack patterns abuse exactly the kind of access orgo_scroll gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Orgo MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for orgo_scroll:
{
"version": "1",
"default": "deny",
"tools": {
"orgo_scroll": {
"limits": [
{
"counter": "orgo_scroll_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} orgo_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 the VM display up or down. Use to navigate long pages, lists, or chat threads in the GUI. It is categorised as a Execute tool in the Orgo MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Orgo MCP Server MCP server in PolicyLayer and add a rule for orgo_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 Orgo MCP Server. Nothing to install.
orgo_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 orgo_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 orgo_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.
orgo_scroll is provided by the Orgo MCP Server MCP server (nickvasilescu/orgo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Orgo MCP Server, 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.
28 Orgo MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.