stop_sstimap_interactive

What stop_sstimap_interactive does on Pentester-MCP

AI agents invoke stop_sstimap_interactive 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_sstimap_interactive is rated High

This tool executes a process termination command (kill/stop by PID), which is a form of code/system execution. While not destructive in the data-loss sense, it forcibly terminates an active session and could disrupt legitimate testing workflows or dependent operations. The high severity reflects that misuse could halt critical security assessments or cause unexpected state changes in the testing environment.

From the tool's definition Terminates a background sstimap session using its PID — sstimap is a server-side template injection testing tool. Stopping a process by PID is a system-level execution action that modifies runtime state.

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

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

Questions about stop_sstimap_interactive