stop_sqlmap_os_shell

What stop_sqlmap_os_shell does on Pentester-MCP

AI agents invoke stop_sqlmap_os_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_sqlmap_os_shell is rated High

While the tool itself performs termination (which might superficially appear as a control action), it operates on an os-shell process—a live execution context spawned by sqlmap for arbitrary command execution. In the context of a penetration testing framework, managing os-shell processes inherently relates to Execute category: the tool controls access to code/command execution capabilities.

From the tool's definition Tool terminates a background sqlmap os-shell process. The description indicates it manages an active os-shell context created by sqlmap, which is a SQL injection exploitation tool that executes arbitrary operating system commands.

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

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

Questions about stop_sqlmap_os_shell