stop_wp_shell

What stop_wp_shell does on Pentester-MCP

AI agents invoke stop_wp_shell 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.

Why stop_wp_shell is rated High

This tool executes a system-level command to terminate a background shell process used in web exploitation attacks. While termination might appear reversible in isolation, in a penetration testing context it terminates active exploit shells—a consequential operation that triggers external effects (process termination) dependent on the supplied PID argument.

From the tool's definition Tool name 'stop_wp_shell' and description 'Terminates a background wp shell process by PID' indicate termination of a wp (WordPress exploitation) shell process. The server context describes 'open-source penetration testing tools' including 'web exploitation'.

The rule that runs stop_wp_shell 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_wp_shell, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "stop_wp_shell": {
      "limits": [
        {
          "counter": "stop_wp_shell_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

Questions about stop_wp_shell