refactor_to_pom | PolicyLayer

WHAT IT DOES

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

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

This tool creates or modifies test code reversibly—it refactors existing migrated Playwright tests and generates new page object class files. These are write operations that can be reversed (files can be edited or regenerated).

From the tool's definition Tool description states it 'Refactors...to use Page Object Model pattern' and 'Extracts actual selectors and creates proper page object classes with methods,' indicating it modifies test code structure and creates new files/classes.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

refactor_to_pom Rate-limited

refactor_to_pom 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": {
    "refactor_to_pom": {
      "limits": [
        {
          "counter": "refactor_to_pom_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 refactor_to_pom

What does the refactor_to_pom tool do? +

Refactors a migrated Playwright test to use Page Object Model pattern. Extracts actual selectors and creates proper page object classes with methods. 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 refactor_to_pom? +

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

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

Can I rate-limit refactor_to_pom? +

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

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

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