hping3_scan
AI agents invoke hping3_scan to trigger actions in Kali Linux MCP Server. 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.
hping3 is a well-known active network tool that can craft and send arbitrary packets, conduct SYN floods, traceroutes, and port scans against external targets. Even though the description is empty, the tool name and server context (penetration testing, 60+ Kali Linux tools) strongly imply Execute-level capabilities with high blast radius — it can be used to attack or disrupt remote systems.
From the tool's definition Tool name 'hping3_scan' on a Kali Linux penetration testing server. hping3 is a network tool capable of sending arbitrary TCP/IP packets, performing port scanning, DoS attacks, and firewall testing.
Attacks that exploit this kind of access
hping3_scan. It is categorised as a Execute tool in the Kali Linux MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Kali Linux MCP Server MCP server in PolicyLayer and add a rule for hping3_scan: 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 Kali Linux MCP Server. Nothing to install.
hping3_scan 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 hping3_scan 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 hping3_scan. 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.
hping3_scan is provided by the Kali Linux MCP Server MCP server (ofryma/custom-mcp-library). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →