scroll_to_element · React Devtools MCP: Risk & Policy

WHAT IT DOES

What scroll_to_element does on React Devtools

AI agents invoke scroll_to_element to trigger actions in React Devtools. 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_to_element needs a policy

This tool causes a side effect in the running application by programmatically scrolling the UI to bring an element into view. This is an interactive browser/app action rather than a pure read operation, placing it in the Execute category. Misuse could disrupt user experience or be used to manipulate visible UI state, warranting medium severity.

From the tool's definition 'Scroll the app to show an element' — triggers an external browser/app action that manipulates the UI viewport

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

scroll_to_element Rate-limited

scroll_to_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_to_element": {
      "limits": [
        {
          "counter": "scroll_to_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 React Devtools, so you can run agents against it safely.

FAQ

Questions about scroll_to_element

What does the scroll_to_element tool do? +

Scroll the app to show an element. It is categorised as a Execute tool in the React Devtools 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_to_element? +

Register the React Devtools MCP server in PolicyLayer and add a rule for scroll_to_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 React Devtools. Nothing to install.

What risk level is scroll_to_element? +

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

Can I rate-limit scroll_to_element? +

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

Set action: deny in the PolicyLayer policy for scroll_to_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_to_element? +

scroll_to_element is provided by the React Devtools MCP server (skylarbarrera/react-devtools-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.