AI agents invoke wfuzz_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.
wfuzz is a web fuzzing/brute-force tool that actively sends large volumes of crafted HTTP requests to target systems. It executes external network operations against web targets, which can include credential brute-forcing and directory enumeration. The description is empty, lowering confidence slightly, but the tool name and server context strongly imply active execution against external systems.
From the tool's definition Tool name 'wfuzz_scan' on a Kali Linux penetration testing server supporting 'web扫描' (web scanning) and '密码攻击' (password attacks). wfuzz is a well-known web application fuzzer used for brute-forcing parameters, directories, and credentials.
Attacks that exploit this kind of access
wfuzz_scan. 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 wfuzz_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.
wfuzz_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 wfuzz_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 wfuzz_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.
wfuzz_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 →