AI agents invoke wafw00f_scan to trigger actions in Kali. 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.
wafw00f is a Web Application Firewall detection/fingerprinting tool that actively probes remote targets. It falls under Execute because it runs an external security tool whose effects depend on the provided arguments (target URLs/IPs). While wafw00f is primarily a reconnaissance tool, it sends active probes to external systems, which could be considered unauthorized access if misused.
From the tool's definition 'Execute wafw00f with the provided parameters' — runs the wafw00f WAF fingerprinting tool against external targets; part of a Kali Linux penetration testing server supporting 'network scanning, web scanning, password attacks'
Attacks that exploit this kind of access
Execute wafw00f with the provided parameters. It is categorised as a Execute tool in the Kali MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Kali MCP server in PolicyLayer and add a rule for wafw00f_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. Nothing to install.
wafw00f_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 wafw00f_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 wafw00f_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.
wafw00f_scan is provided by the Kali MCP server (pentestt00ls/kali-mcp-server). 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 →