stop_phpsploit_session

What stop_phpsploit_session does on Pentester-MCP

AI agents invoke stop_phpsploit_session 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_phpsploit_session is rated High

This tool executes a process termination command targeting an active phpsploit session. While termination itself is less severe than initiating an exploit, it triggers external operation (process management) whose consequences depend on which session is targeted. The tool operates within a penetration testing context where phpsploit sessions represent active compromise points.

From the tool's definition Tool name 'stop_phpsploit_session' and description 'Terminates a background phpsploit session using its Process ID (PID)' indicate termination of an active exploitation framework session. Phpsploit is a remote code execution tool used in penetration testing.

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

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

Questions about stop_phpsploit_session