Low Risk

e2e_get_actions

Get the action timeline for a test run. Shows what happened step-by-step.

How to control e2e_get_actions ↓

What e2e_get_actions does on Playwright Autopilot

AI agents call e2e_get_actions 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_get_actions needs a policy

This tool retrieves and displays a log or timeline of actions that occurred during a past test run. It is a pure read operation that queries execution history without modifying any state, triggering new actions, or affecting the system under test. The 'get' verb and passive 'shows what happened' language confirm read-only semantics.

From the tool's definition Tool name 'e2e_get_actions' and description 'Get the action timeline for a test run. Shows what happened step-by-step' indicate retrieval of historical test execution data with no modification or side effects.

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

How to control e2e_get_actions

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

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

e2e_get_actions 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_get_actions

What does the e2e_get_actions tool do? +

Get the action timeline for a test run. Shows what happened step-by-step. 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_get_actions? +

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

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

Can I rate-limit e2e_get_actions? +

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

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

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