migrate_config | PolicyLayer

WHAT IT DOES

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

AI agents use migrate_config 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_config needs a policy

The tool modifies or creates configuration files by converting WDIO config to Playwright config format. This is a Write operation because it creates or updates configuration files. However, it states 'Preserves existing Playwright config if present,' which mitigates some risk of unintended overwrites.

From the tool's definition Migrates wdio.conf.js to playwright.config.ts. Preserves existing Playwright config if present.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

migrate_config Rate-limited

migrate_config 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_config": {
      "limits": [
        {
          "counter": "migrate_config_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_config

What does the migrate_config tool do? +

Migrates wdio.conf.js to playwright.config.ts. Preserves existing Playwright config if present. 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_config? +

Register the MCP Server - Test Migration (WDIO to Playwright) MCP server in PolicyLayer and add a rule for migrate_config: 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_config? +

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

Can I rate-limit migrate_config? +

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

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

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