scroll · Rn Debug MCP: Risk & Policy

WHAT IT DOES

What scroll does on Rn Debug

AI agents invoke scroll to trigger actions in Rn Debug. 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 needs a policy

This tool performs a UI interaction (swipe gesture) on a connected app/device, triggering an external operation that causes the screen to scroll. It is not a simple read, write, or destructive action — it executes a gesture-based interaction whose effects depend on the arguments (direction, amount). Misuse could cause unintended navigation or UI state changes in the connected application.

From the tool's definition Scroll screen content in a direction via swipe gesture

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

scroll Rate-limited

scroll 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": {
      "limits": [
        {
          "counter": "scroll_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 Rn Debug, so you can run agents against it safely.

FAQ

Questions about scroll

What does the scroll tool do? +

Scroll screen content in a direction via swipe gesture. It is categorised as a Execute tool in the Rn Debug 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? +

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

What risk level is scroll? +

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

Can I rate-limit scroll? +

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

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

scroll is provided by the Rn Debug MCP server (rn-debug-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.