e2e_save_app_flow

ServerPlaywright Autopilot
CategoryWrite

WHAT IT DOES

What e2e_save_app_flow does on Playwright Autopilot

AI agents use e2e_save_app_flow to create or update resources in Playwright Autopilot — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Playwright Autopilot environment.

THE RISK

Medium Risk

Why e2e_save_app_flow needs a policy

This tool writes structured data to persistent storage (.e2e-flows.json). While the action is reversible (flows can be overwritten or deleted), it modifies application state and testing configuration.

From the tool's definition The tool 'e2e_save_app_flow' creates or modifies data by saving application flows to a .e2e-flows.json file. The description explicitly states it 'Updates existing flows by flowName', indicating reversible creation/modification of stored data.

Documented attack patterns abuse exactly the kind of access e2e_save_app_flow gives an agent:

POLICY

How to control e2e_save_app_flow

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_save_app_flow:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "e2e_save_app_flow": {
      "limits": [
        {
          "counter": "e2e_save_app_flow_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

e2e_save_app_flow stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

Create a free account and register Playwright Autopilot — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Playwright Autopilot tools

Execute browser_batch Execute multiple browser actions in one call. PREFERRED over individual click/type calls \ Execute browser_navigate Navigate to a URL in the browser. Launches the browser if not already open. Execute browser_navigate_back Navigate back in browser history. Execute e2e_build_flows Run each test individually with action capture and auto-save flows. Discovers all tests (o Execute e2e_run_test Run Playwright tests. When location is provided, runs a specific test with action capture Execute e2e_start_flow Start recording a browser exploration flow. Every browser action (navigate, click, type, e Execute browser_hover Hover over an element on the page. Execute browser_replay_flow Replay saved flows using stored locators \u2014 no ARIA snapshots returned. Minimal token

All 51 Playwright Autopilot tools →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about e2e_save_app_flow

What does the e2e_save_app_flow tool do? +

Save a confirmed application flow to .e2e-flows.json. The flow must include confirmed: true to indicate the user has verified it. Updates existing flows by flowName. Use a naming convention for variants:. It is categorised as a Write tool in the Playwright Autopilot MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on e2e_save_app_flow? +

Register the Playwright Autopilot MCP server in PolicyLayer and add a rule for e2e_save_app_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.

What risk level is e2e_save_app_flow? +

e2e_save_app_flow is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit e2e_save_app_flow? +

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

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

e2e_save_app_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.

Enforce policy on every Playwright Autopilot tool call.

Start from Playwright Autopilot, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →

Free to start. No card required.

51 Playwright Autopilot tools catalogued and risk-classified — across an index of 43,000+ MCP servers.