register_custom_commands

WHAT IT DOES

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

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

This tool creates or modifies migration configuration data (custom command registrations) that affects subsequent transformations, making it a Write operation. The severity is medium because misuse could create incorrect command mappings that break tests, but the impact is scoped to the migration configuration rather than production systems.

From the tool's definition Tool name 'register_custom_commands' and description 'Registers custom WDIO commands with their Playwright equivalents' indicate persistent storage of mapping configurations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

register_custom_commands Rate-limited

register_custom_commands 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": {
    "register_custom_commands": {
      "limits": [
        {
          "counter": "register_custom_commands_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 register_custom_commands

What does the register_custom_commands tool do? +

Registers custom WDIO commands with their Playwright equivalents for migration. Allows handling project-specific custom commands. 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 register_custom_commands? +

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

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

Can I rate-limit register_custom_commands? +

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

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

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