Ping a host and return the raw output.
AI agents invoke ping_host to trigger actions in Nmap. 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.
This tool runs an active network operation (ping) against a target host, which constitutes executing an external command with real network effects. While ping is generally low-impact, it can be used for reconnaissance, host discovery, or even as part of a DoS amplification. Running inside Docker provides some isolation, but the network activity itself is real and outbound.
From the tool's definition 'Ping a host and return the raw output' — executes a network ping command against an external host
Documented attack patterns abuse exactly the kind of access ping_host gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Nmap, and nothing reaches the server without passing your rules. This is the rule we recommend for ping_host:
{
"version": "1",
"default": "deny",
"tools": {
"ping_host": {
"limits": [
{
"counter": "ping_host_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}ping_host stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Ping a host and return the raw output. It is categorised as a Execute tool in the Nmap MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Nmap MCP server in PolicyLayer and add a rule for ping_host: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Nmap. Nothing to install.
ping_host is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the ping_host rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for ping_host. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
ping_host is provided by the Nmap MCP server (jarrodcoulter/nmap-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Nmap, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
5 Nmap tools catalogued and risk-classified — across an index of 43,000+ MCP servers.