stop_php_server

Terminate a background PHP development server using its Process ID (PID).

SERVERPentester-MCP SOURCEhalilkirazkaya/pentester-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/halilkirazkaya-pentester-mcp/stop-php-server.md

WHAT IT DOES

What stop_php_server does on Pentester-MCP

AI agents invoke stop_php_server to trigger actions in Pentester-MCP. 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.

RISK

Why stop_php_server is rated High

This tool executes a command to stop a running PHP server process. While not destructive (the server can be restarted), it is an Execute action because it triggers an external operation (process termination) whose effects depend on the PID argument supplied. In a penetration testing context where the server may be part of a target application or test infrastructure, unauthorized termination could disrupt services.

From the tool's definition Tool terminates a background PHP development server using its Process ID (PID). The description indicates execution of a process termination command that affects running system processes.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs stop_php_server safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Pentester-MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For stop_php_server, this is the rule to start with:

stop_php_server Rate-limited

stop_php_server 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": {
    "stop_php_server": {
      "limits": [
        {
          "counter": "stop_php_server_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Pentester-MCP, apply this rule, and every stop_php_server call is checked against it from then on.

FAQ

Questions about stop_php_server

What does the stop_php_server tool do? +

Terminate a background PHP development server using its Process ID (PID). It is categorised as a Execute tool in the Pentester-MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on stop_php_server? +

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

What risk level is stop_php_server? +

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

Can I rate-limit stop_php_server? +

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

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

stop_php_server is provided by the Pentester MCP server (halilkirazkaya/pentester-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Pentester, and thousands of servers like it.

This server

All 337 Pentester tools → High-risk tools on this server →

Across the catalogue

stop_emba_scan on EMBA-MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →