migrate_to_playwright

WHAT IT DOES

What migrate_to_playwright does on MCP Server - Test Migration (WDIO to Playwright)

AI agents use migrate_to_playwright to create or update resources in MCP Server - Test Migration (WDIO to Playwright) — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Server - Test Migration (WDIO to Playwright) environment.

WHY IT NEEDS A POLICY

Why migrate_to_playwright needs a policy

This tool modifies test files by transforming their syntax and structure (AST-based transformation), which is a Write operation. It does not execute tests (Execute), delete files (Destructive), or access financial systems (Financial).

From the tool's definition Tool description states it 'Migrates a WebDriverIO test to Playwright syntax' and 'refactor[s]' code, 'preserves already-migrated code', and 'Supports TypeScript output' — these are reversible code modifications that create or update test files without…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

migrate_to_playwright Rate-limited

migrate_to_playwright 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": {
    "migrate_to_playwright": {
      "limits": [
        {
          "counter": "migrate_to_playwright_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 MCP Server - Test Migration (WDIO to Playwright), so you can run agents against it safely.

FAQ

Questions about migrate_to_playwright

What does the migrate_to_playwright tool do? +

Migrates a WebDriverIO test to Playwright syntax using AST transformation. Supports partial migrations and preserves already-migrated code. Uses modern Playwright locators (getByRole, getByLabel, getByTestId with data-test-id). Supports TypeScript output. It is categorised as a Write tool in the MCP Server - Test Migration (WDIO to Playwright) MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on migrate_to_playwright? +

Register the MCP Server - Test Migration (WDIO to Playwright) MCP server in PolicyLayer and add a rule for migrate_to_playwright: 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 MCP Server - Test Migration (WDIO to Playwright). Nothing to install.

What risk level is migrate_to_playwright? +

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

Can I rate-limit migrate_to_playwright? +

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

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

migrate_to_playwright is provided by the MCP Server - Test Migration (WDIO to Playwright) MCP server (lucad87/mcp-server-tests-migration). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.