// MCP TOOL REFERENCE

e2e_explore

ServerPlaywright Autopilot
CategoryExecute

WHAT IT DOES

What e2e_explore does on Playwright Autopilot

AI agents invoke e2e_explore 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.

THE RISK

High Risk

Why e2e_explore needs a policy

This tool drives a headless browser (Playwright) to crawl and interact with a web application, executing real browser actions. While its primary purpose is discovery/reading, it actively executes browser operations, navigates pages, and triggers network calls against a live application.

From the tool's definition Automatically crawl a web app...Uses headless Playwright...Returns an app map with layout, actions, and navigation graph

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

POLICY

How to control e2e_explore

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

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "e2e_explore": {
      "limits": [
        {
          "counter": "e2e_explore_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

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

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.

RATE-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 →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in Playwright Autopilot → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about e2e_explore

What does the e2e_explore tool do? +

Automatically crawl a web app to discover page templates, navigation flows, and API calls. Uses headless Playwright with ARIA snapshots (no images) and structural similarity for deduplication. Returns an app map with layout, actions, and navigation graph. 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.

How do I enforce a policy on e2e_explore? +

Register the Playwright Autopilot MCP server in PolicyLayer and add a rule for e2e_explore: 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_explore? +

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

Can I rate-limit e2e_explore? +

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

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

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