Scroll down the page by a pixel amount - if no pixels are specified, scrolls down one page
AI agents invoke scroll_down to trigger actions in Steel 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 interaction/execution action. While it has minimal blast radius on its own, it drives browser navigation state and is part of an automated web control framework. It fits Execute as it triggers an external operation in a live browser, not merely reading or writing data.
From the tool's definition 'Scroll down the page by a pixel amount' — triggers a browser action (scrolling) via Puppeteer in an external browser session
Documented attack patterns abuse exactly the kind of access scroll_down gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Steel MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for scroll_down:
{
"version": "1",
"default": "deny",
"tools": {
"scroll_down": {
"limits": [
{
"counter": "scroll_down_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}scroll_down 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 down the page by a pixel amount - if no pixels are specified, scrolls down one page. It is categorised as a Execute tool in the Steel MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Steel MCP Server MCP server in PolicyLayer and add a rule for scroll_down: 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 Steel MCP Server. Nothing to install.
scroll_down 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_down 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_down. 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_down is provided by the Steel MCP Server MCP server (steel-dev/steel-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 9 Steel MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
9 Steel MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.