Replay saved flows using stored locators \u2014 no ARIA snapshots returned. Minimal token usage. On failure, captures snapshot at the failing step for diagnosis. Chain multiple flows as building blocks.
AI agents invoke browser_replay_flow to trigger actions in Playwright Autopilot. 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.
This tool replays previously recorded browser interaction flows, meaning it executes a series of automated browser actions. Since it can chain multiple flows and trigger any combination of browser operations (navigation, clicks, form submissions, file uploads), it has significant blast radius if misused against unintended targets or with malicious flows.
From the tool's definition Replay saved flows using stored locators — executes sequences of browser actions (clicks, navigation, form fills, etc.) automatically
Documented attack patterns abuse exactly the kind of access browser_replay_flow gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Playwright Autopilot, and nothing reaches the server without passing your rules. This is the rule we recommend for browser_replay_flow:
{
"version": "1",
"default": "deny",
"tools": {
"browser_replay_flow": {
"limits": [
{
"counter": "browser_replay_flow_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}browser_replay_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.
Free to start. No card required.
Replay saved flows using stored locators \u2014 no ARIA snapshots returned. Minimal token usage. On failure, captures snapshot at the failing step for diagnosis. Chain multiple flows as building blocks. It is categorised as a Execute tool in the Playwright Autopilot MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Playwright Autopilot MCP server in PolicyLayer and add a rule for browser_replay_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 Playwright Autopilot. Nothing to install.
browser_replay_flow is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the browser_replay_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 browser_replay_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.
browser_replay_flow is provided by the Playwright Autopilot MCP server (kaizen-yutani/playwright-autopilot). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Playwright Autopilot, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
51 Playwright Autopilot tools catalogued and risk-classified — across an index of 43,000+ MCP servers.