Persist a page interaction flow draft for later replay and evidence reuse.
AI agents use record_page_flow to create or update resources in JS Reverse MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your JS Reverse MCP environment.
The tool writes/stores a recorded page interaction flow draft to persistent storage for later use. This is a Write operation as it creates/saves data. It doesn't execute code directly or delete data, though the stored flows could later be replayed (execute), the act of recording/persisting is Write. Severity is medium as misuse could store malicious interaction flows for replay attacks.
From the tool's definition Persist a page interaction flow draft for later replay and evidence reuse
Attacks that exploit this kind of access
Persist a page interaction flow draft for later replay and evidence reuse. It is categorised as a Write tool in the JS Reverse MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the JS Reverse MCP server in PolicyLayer and add a rule for record_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.
record_page_flow is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the record_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.
Set action: deny in the PolicyLayer policy for record_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.
record_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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →