Read stored application flows from .e2e-flows.json. Flows describe confirmed user journeys (e.g.
AI agents call e2e_get_app_flows to retrieve information from Playwright Autopilot without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries stored test flow data for inspection and analysis purposes. It has no side effects, does not execute flows or external code, does not modify data, and does not delete anything. It is purely informational, falling squarely into the Read category.
From the tool's definition Tool name 'e2e_get_app_flows' and description 'Read stored application flows from .e2e-flows.json' explicitly indicate retrieval of pre-existing test flow definitions with no modification, deletion, or execution of external systems.
Documented attack patterns abuse exactly the kind of access e2e_get_app_flows 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 e2e_get_app_flows:
{
"version": "1",
"default": "deny",
"tools": {
"e2e_get_app_flows": {}
}
} e2e_get_app_flows is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Read stored application flows from .e2e-flows.json. Flows describe confirmed user journeys (e.g. It is categorised as a Read tool in the Playwright Autopilot MCP Server, which means it retrieves data without modifying state.
Register the Playwright Autopilot MCP server in PolicyLayer and add a rule for e2e_get_app_flows: 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.
e2e_get_app_flows is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the e2e_get_app_flows 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 e2e_get_app_flows. 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.
e2e_get_app_flows 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.