browser_e2e · Limetest MCP Server MCP: Risk & Policy

WHAT IT DOES

What browser_e2e does on Limetest MCP Server

AI agents invoke browser_e2e to trigger actions in Limetest MCP Server. 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.

WHY IT NEEDS A POLICY

Why browser_e2e needs a policy

This tool runs arbitrary browser automation operations whose side effects depend entirely on test case definitions provided by the user/AI agent. It can interact with web applications in ways that modify state (form submissions, clicks on action buttons, navigation), trigger external services, or perform unintended actions if test cases are malicious or misaligned.

From the tool's definition Tool name 'browser_e2e' and description 'Execute End to End automation test in the browser' — the word 'Execute' is explicit.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

browser_e2e Rate-limited

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

View as policy code

policy.json

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

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Limetest MCP Server, so you can run agents against it safely.

FAQ

Questions about browser_e2e

What does the browser_e2e tool do? +

Execute End to End automation test in the browser. It is categorised as a Execute tool in the Limetest MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on browser_e2e? +

Register the Limetest MCP Server MCP server in PolicyLayer and add a rule for browser_e2e: 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 Limetest MCP Server. Nothing to install.

What risk level is browser_e2e? +

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

Can I rate-limit browser_e2e? +

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

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

browser_e2e is provided by the Limetest MCP Server MCP server (m2rads/limetest-arch). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.