scroll_element · MacWright MCP: Risk & Policy

WHAT IT DOES

What scroll_element does on MacWright

AI agents invoke scroll_element to trigger actions in MacWright. 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.

WHY IT NEEDS A POLICY

Why scroll_element needs a policy

This tool performs a browser action (scrolling a DOM element in Safari), which is an external operation that interacts with a running application. It doesn't just read data, it triggers a UI/browser action whose effects depend on arguments. It's not destructive or financial, but it is an execution of an external operation, fitting the Execute category.

From the tool's definition Scroll a specific DOM element (overflow container) in Safari — for scrolling inside a div with overflow:auto/scroll, not the page

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

scroll_element Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "scroll_element": {
      "limits": [
        {
          "counter": "scroll_element_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches MacWright, so you can run agents against it safely.

FAQ

Questions about scroll_element

What does the scroll_element tool do? +

Scroll a specific DOM element (overflow container) in Safari — for scrolling inside a div with overflow:auto/scroll, not the page. Returns new scrollTop/scrollLeft. It is categorised as a Execute tool in the MacWright 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_element? +

Register the MacWright MCP server in PolicyLayer and add a rule for scroll_element: 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 MacWright. Nothing to install.

What risk level is scroll_element? +

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

Can I rate-limit scroll_element? +

Yes. Add a rate_limit block to the scroll_element 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_element completely? +

Set action: deny in the PolicyLayer policy for scroll_element. 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_element? +

scroll_element is provided by the MacWright MCP server (ruchit-p/macwright). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.