replay_page_flow · JS Reverse MCP: Risk & Policy

WHAT IT DOES

What replay_page_flow does on JS Reverse MCP

AI agents invoke replay_page_flow to trigger actions in JS Reverse MCP. 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 replay_page_flow needs a policy

Replaying a page flow executes a sequence of browser actions (e.g., clicks, navigation, form inputs) in an automated fashion. This constitutes external operation execution whose effects depend on the recorded actions and the current page state. Misuse could trigger unintended side effects on web applications, such as submitting forms, making purchases, or modifying account data.

From the tool's definition 'Replay recorded page flow actions through PageController' — replays browser actions (clicks, navigation, form submissions, etc.) automatically in a live browser session

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

replay_page_flow Rate-limited

replay_page_flow 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": {
    "replay_page_flow": {
      "limits": [
        {
          "counter": "replay_page_flow_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 JS Reverse MCP, so you can run agents against it safely.

FAQ

Questions about replay_page_flow

What does the replay_page_flow tool do? +

Replay recorded page flow actions through PageController. It is categorised as a Execute tool in the JS Reverse MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on replay_page_flow? +

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

What risk level is replay_page_flow? +

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

Can I rate-limit replay_page_flow? +

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

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

replay_page_flow is provided by the JS Reverse MCP server (noone-hub/jsreverser-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.