High Risk →

scroll_up

Scroll up the page by a pixel amount - if no pixels are specified, scrolls up one page

How to control scroll_up ↓

AI agents invoke scroll_up 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.

High Risk

This tool performs a browser action (scrolling) within a Puppeteer-controlled browser session. It triggers an external operation in a live browser environment, classifying it as Execute. The blast radius is low as scrolling is a benign navigation action with no data modification or destructive potential.

From the tool's definition Scroll up the page by a pixel amount - if no pixels are specified, scrolls up one page

Documented attack patterns abuse exactly the kind of access scroll_up 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_up:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "scroll_up": {
      "limits": [
        {
          "counter": "scroll_up_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

scroll_up 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.

  1. Create a free account and register Steel MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RATE-LIMIT THIS TOOL →

Free to start. No card required.

Go deeper

What does the scroll_up tool do? +

Scroll up the page by a pixel amount - if no pixels are specified, scrolls up 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.

How do I enforce a policy on scroll_up? +

Register the Steel MCP Server MCP server in PolicyLayer and add a rule for scroll_up: 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.

What risk level is scroll_up? +

scroll_up is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit scroll_up? +

Yes. Add a rate_limit block to the scroll_up 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.

How do I block scroll_up completely? +

Set action: deny in the PolicyLayer policy for scroll_up. 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.

What MCP server provides scroll_up? +

scroll_up 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.

Enforce policy on every Steel MCP Server tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.