stop_ssrfmap_handler

What stop_ssrfmap_handler does on Pentester-MCP

AI agents invoke stop_ssrfmap_handler 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_ssrfmap_handler is rated High

This tool executes a command to terminate a running process. While termination itself appears reversible (the process can be restarted), it is fundamentally an Execute action that triggers system-level operations whose effects depend on which handler process is targeted. The context (Pentester-MCP with ssrfmap for SSRF exploitation) indicates this interacts with active exploitation tools.

From the tool's definition 'Terminate a background ssrfmap handler process' — stops an external process that performs SSRF (Server-Side Request Forgery) exploitation testing. Process termination is a system-level action that triggers external operations.

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

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

Questions about stop_ssrfmap_handler