run_nping

What run_nping does on Pentester-MCP

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

nping is a command-line network packet crafting and analysis tool that sends custom network packets. Running it constitutes autonomous execution of external network operations whose effects depend on target arguments (destination hosts, packet parameters, protocols). This fits Execute category—it triggers external network operations that are not mere data retrieval.

From the tool's definition Tool is part of a penetration testing server explicitly designed to 'autonomously execute over 200 open-source penetration testing tools' including 'reconnaissance, web exploitation, and brute-forcing.' The tool name 'run_nping' indicates execution of nping…

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

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

Questions about run_nping