PLAYWRIGHT AUTOPILOT TOOLS

51 tools from the Playwright Autopilot MCP Server, categorised by risk level.

READ 25 tools
Read browser_snapshot Capture the full ARIA accessibility snapshot of the current page. Returns the complete page structure with ... Read browser_take_screenshot Take a screenshot of the current page. Saves to a file and returns the file path by default. Use Read e2e_discover_flows Scan all spec files and extract the sequence of page-object method calls per test. Use this when no flows a... Read e2e_find_elements Search the DOM snapshot for elements matching a role or text. Much cheaper than loading a full DOM snapshot... Read e2e_get_action_detail Get full detail for a single action including DOM snapshots, timing, params, error. Read e2e_get_actions Get the action timeline for a test run. Shows what happened step-by-step. Read e2e_get_app_flows Read stored application flows from .e2e-flows.json. Flows describe confirmed user journeys (e.g. Read e2e_get_console Get console output from a test run. Optionally filter by type (error, warn, log, info). Read e2e_get_context Lightweight project overview: flow names with descriptions + page object class names with method counts. Use Read e2e_get_dom_diff Get the DOM diff (added/removed/changed elements) for a specific action. Read e2e_get_dom_snapshot Get the DOM snapshot before and/or after a specific action. Use interactiveOnly=true to get only inputs/but... Read e2e_get_evidence_bundle Get ALL failure evidence for a test in one call \u2014 error, steps to reproduce, action timeline, network,... Read e2e_get_failure_report Get a failure report for a test run. Returns error, failing action details, action timeline, failed network... Read e2e_get_network Get network requests from a test run. Optionally filter by URL pattern, method, or status code. Response bo... Read e2e_get_screenshot Get a failure screenshot as a base64 image. Returns the image content that Claude can display. Read e2e_get_stats Get E2E suite health statistics: pass rate trend, flaky tests ranked by score, failure category breakdown, ... Read e2e_get_test_source Read the test source file. With resolve=true, returns only the test body plus referenced page object method... Read e2e_get_triage_config Read the triage configuration from .e2e-triage.json. Returns Jira settings, flaky thresholds, and project f... Read e2e_impact_analysis Find all tests that use a specific page object method. Use before refactoring to see what will break. Read e2e_list_flows List all saved flow recordings from previous exploration sessions. Read e2e_list_projects List available Playwright projects from the config. Returns project names that can be used with the project... Read e2e_list_tests Discover available Playwright tests in the project. Returns test files with their test cases and line numbers. Read e2e_match_patterns Search the error pattern database for matches against a failing test. Returns detailed match info including... Read e2e_scan_page_objects Scan all .page.ts and .service.ts files in the project. Returns class names, methods (with @step decorators... Read e2e_suggest_tests Analyze test coverage gaps: untested page object methods, missing flow variants, and uncovered flow steps. ...
EXECUTE 20 tools
Execute browser_batch Execute multiple browser actions in one call. PREFERRED over individual click/type calls \u2014 dramaticall... 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 (optionally filtere... Execute e2e_run_test Run Playwright tests. When location is provided, runs a specific test with action capture for deep debuggin... Execute e2e_start_flow Start recording a browser exploration flow. Every browser action (navigate, click, type, etc.) will be reco... 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 usage. On failure... Execute browser_tabs List, select, or close browser tabs. Actions: Execute e2e_bisect Find the commit that broke a test using behavioral bisection. Runs binary search through git history, compa... Execute e2e_explore Automatically crawl a web app to discover page templates, navigation flows, and API calls. Uses headless Pl... Execute browser_click Click an element on the page. For multiple clicks, prefer browser_batch instead. Execute browser_close Close the browser and clean up resources. Execute browser_file_upload Upload one or more files to a file chooser. The file chooser must be visible first (triggered by clicking a... Execute browser_fill_form Fill multiple form fields in one call. Fields can be addressed by ref (from snapshot) or by label (accessib... Execute browser_press_key Press a key or key combination (e.g. Enter, Escape, Tab, ArrowDown, Control+a). Execute browser_restore_session Restore a previously saved browser session. Creates a new browser context with saved cookies/localStorage, ... Execute browser_select_option Select an option from a dropdown element. Execute browser_set_headers Set extra HTTP headers for browser requests. Headers are automatically scoped to same-origin requests only,... Execute browser_type Type text into an input field. For multiple fields, prefer browser_fill_form or browser_batch instead.

Route Playwright Autopilot through PolicyLayer and every one of its 51 tools is checked against your policy before it runs.

CHECK YOUR STACK →

See every tool, the dangerous ones, and the token cost across your stack.

How many tools does the Playwright Autopilot MCP server have? +

The Playwright Autopilot MCP server exposes 51 tools across 3 categories: Read, Write, Execute.

How do I enforce policies on Playwright Autopilot tools? +

Route the Playwright Autopilot server through the PolicyLayer gateway. Define allow, deny, or approval rules per tool in the dashboard; they are enforced on every call before it reaches the server.

What risk categories do Playwright Autopilot tools fall into? +

Playwright Autopilot tools are categorised as Read (25), Write (6), Execute (20). Each category has a recommended default policy.

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.

Free to start. No card required.

43,000+ MCP servers and 220,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.