phpactor_index_build · Phpactor MCP Server MCP

WHAT IT DOES

What phpactor_index_build does on Phpactor MCP Server

AI agents invoke phpactor_index_build to trigger actions in Phpactor MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why phpactor_index_build needs a policy

This tool executes a build/indexing operation that modifies the state of the Phpactor project index, which is a prerequisite for other tools. While it doesn't irreversibly delete data (not Destructive) or create persistent new project artifacts (not Write in the reversible sense), it runs a process whose effects are contingent on the project configuration and whose execution can have side effects (warnings, index…

From the tool's definition Tool description states it 'Build or rebuild the Phpactor project index' and 'Must run before other phpactor tools.' The verb 'build' combined with the operational nature of constructing an index and the dependency relationship ('must run before') indicates…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

phpactor_index_build Rate-limited

phpactor_index_build stays usable, but rate-capped — a runaway agent can't fire it dozens of times 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_index_build": {
      "limits": [
        {
          "counter": "phpactor_index_build_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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_index_build

What does the phpactor_index_build tool do? +

Build or rebuild the Phpactor project index. Must run before other phpactor tools. Checks PSR-4 autoload config and warns if missing (Yii2 projects need manual setup). It is categorised as a Execute tool in the Phpactor MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on phpactor_index_build? +

Register the Phpactor MCP Server MCP server in PolicyLayer and add a rule for phpactor_index_build: 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_index_build? +

phpactor_index_build is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit phpactor_index_build? +

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

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

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