Low Risk

e2e_list_tests

Discover available Playwright tests in the project. Returns test files with their test cases and line numbers.

How to control e2e_list_tests ↓

What e2e_list_tests does on Playwright Autopilot

AI agents call e2e_list_tests 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.

Low Risk

Why e2e_list_tests needs a policy

This tool performs a read-only discovery operation—it lists and returns information about existing test files and their structure. It has no side effects, does not execute tests, does not modify files, and does not trigger external actions. It is purely informational retrieval, placing it squarely in the Read category with low severity.

From the tool's definition Tool name 'e2e_list_tests' and description 'Discover available Playwright tests in the project. Returns test files with their test cases and line numbers' indicate a query/discovery operation that retrieves metadata about test files without modifying or…

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

How to control e2e_list_tests

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "e2e_list_tests": {}
  }
}

e2e_list_tests is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

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

Free to start. No card required.

Related tools and policies

Go deeper

Questions about e2e_list_tests

What does the e2e_list_tests tool do? +

Discover available Playwright tests in the project. Returns test files with their test cases and line numbers. It is categorised as a Read tool in the Playwright Autopilot MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on e2e_list_tests? +

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

e2e_list_tests is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit e2e_list_tests? +

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

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

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

Free to start. No card required.

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

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.