phpactor_rename_class · Phpactor MCP Server MCP

WHAT IT DOES

What phpactor_rename_class does on Phpactor MCP Server

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

WHY IT NEEDS A POLICY

Why phpactor_rename_class needs a policy

This tool creates or modifies data (PHP source code) across the project, changing class references in multiple locations. While the changes are technically reversible (code can be reverted), the scope is broad and could affect many files simultaneously. It does not delete or irreversibly destroy data, nor does it execute arbitrary code or move files—it purely updates references.

From the tool's definition 'Update all REFERENCES to a PHP class project-wide (use statements, type hints, docblocks, instantiations)' — the tool modifies code across multiple files by changing class references, which is a reversible Write operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

phpactor_rename_class Rate-limited

phpactor_rename_class 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": {
    "phpactor_rename_class": {
      "limits": [
        {
          "counter": "phpactor_rename_class_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 Phpactor MCP Server, so you can run agents against it safely.

FAQ

Questions about phpactor_rename_class

What does the phpactor_rename_class tool do? +

Update all REFERENCES to a PHP class project-wide (use statements, type hints, docblocks, instantiations). Does NOT rename the file or modify the class declaration — use phpactor_move_class for a full rename including file move and namespace update. It is categorised as a Write tool in the Phpactor 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 phpactor_rename_class? +

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

What risk level is phpactor_rename_class? +

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

Can I rate-limit phpactor_rename_class? +

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

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

phpactor_rename_class is provided by the Phpactor MCP Server MCP server (p4it-kft/p4it-phpactor-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.