Advanced web application fuzzer for discovering hidden resources and parameters.
AI agents invoke wfuzz to trigger actions in MCP Kali Pentest. 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 actively sends crafted HTTP requests to external web applications to discover hidden resources, parameters, and vulnerabilities. This constitutes triggering external operations against target systems, making it Execute category. Misuse could cause denial-of-service conditions on target servers, trigger intrusion detection systems, or be used to probe systems without authorization — hence high severity.
From the tool's definition Advanced web application fuzzer for discovering hidden resources and parameters
Attacks that exploit this kind of access
Advanced web application fuzzer for discovering hidden resources and parameters. It is categorised as a Execute tool in the MCP Kali Pentest MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MCP Kali Pentest MCP server in PolicyLayer and add a rule for wfuzz: 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 MCP Kali Pentest. Nothing to install.
wfuzz 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 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. 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 is provided by the MCP Kali Pentest MCP server (root1856/mcpkali). 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 →