AI agents invoke scroll to trigger actions in Wraith. 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 interaction that triggers page-level effects (e.g., lazy-loading content, infinite scroll pagination, triggering JavaScript scroll events). It is an Execute-category action because it performs an external browser operation whose effects depend on the current page state and arguments.
From the tool's definition 'Scroll the page' — triggers a browser action (scrolling) and 'return a new snapshot' indicates it interacts with a live browser session, constituting an external browser operation.
Attacks that exploit this kind of access
Scroll the page, then return a new snapshot. It is categorised as a Execute tool in the Wraith MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Wraith 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 Wraith. 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 Wraith MCP server (koreahwan/wraith-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →