List available Playwright projects from the config. Returns project names that can be used with the project parameter in other tools.
AI agents call e2e_list_projects 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 queries and returns configuration metadata (project names) without any side effects, code execution, or state changes. It is informational only, enabling discovery of available projects for use by other tools. The blast radius of misuse is minimal—an agent could at most learn what projects exist, which is low-risk information.
From the tool's definition Tool name contains 'list' and description states 'List available Playwright projects' and 'Returns project names' — a pure retrieval operation with no modification or execution.
Documented attack patterns abuse exactly the kind of access e2e_list_projects 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_list_projects:
{
"version": "1",
"default": "deny",
"tools": {
"e2e_list_projects": {}
}
}e2e_list_projects 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.
List available Playwright projects from the config. Returns project names that can be used with the project parameter in other tools. 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_list_projects: 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_list_projects 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_list_projects 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_list_projects. 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_list_projects 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.