Scroll the page or scroll to a specific element
AI agents invoke scroll_page to trigger actions in Webclaw. 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 executes a UI action. While it has minimal blast radius and no data modification, it is an active browser control operation rather than a passive read, fitting the Execute category. Misuse risk is low since scrolling itself causes no data changes or destructive effects.
From the tool's definition 'Scroll the page or scroll to a specific element' — triggers a browser action (scrolling) in a real Chrome browser
Documented attack patterns abuse exactly the kind of access scroll_page gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Webclaw, and nothing reaches the server without passing your rules. This is the rule we recommend for scroll_page:
{
"version": "1",
"default": "deny",
"tools": {
"scroll_page": {
"limits": [
{
"counter": "scroll_page_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}scroll_page 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 page or scroll to a specific element. It is categorised as a Execute tool in the Webclaw MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Webclaw MCP server in PolicyLayer and add a rule for scroll_page: 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 Webclaw. Nothing to install.
scroll_page 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_page 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_page. 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_page is provided by the Webclaw MCP server (kuroko1t/webclaw). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Webclaw, 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.
21 Webclaw tools catalogued and risk-classified — across an index of 43,000+ MCP servers.