generate_test · LocatorLabs MCP Server MCP: Risk & Policy

WHAT IT DOES

What generate_test does on LocatorLabs MCP Server

AI agents use generate_test to create or update resources in LocatorLabs MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your LocatorLabs MCP Server environment.

WHY IT NEEDS A POLICY

Why generate_test needs a policy

This tool generates (creates) a test script artifact — it produces code but does not execute it. The output is code that 'can be saved and run independently,' meaning the tool itself only writes/returns the script, not runs it. This is a Write operation. Severity is medium because the generated code could contain executable logic that a user might run without review, but the tool itself does not execute anything.

From the tool's definition Generate a Playwright test script from test steps. Returns executable code that can be saved and run independently.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

generate_test Rate-limited

generate_test stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "generate_test": {
      "limits": [
        {
          "counter": "generate_test_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about generate_test

What does the generate_test tool do? +

Generate a Playwright test script from test steps. Returns executable code that can be saved and run independently. It is categorised as a Write tool in the LocatorLabs MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on generate_test? +

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

What risk level is generate_test? +

generate_test is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit generate_test? +

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

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

generate_test is provided by the LocatorLabs MCP Server MCP server (naveenanimation20/locatorlabs-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.