AI agents invoke gobuster_fuzz to trigger actions in Gobuster. 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 actively sends crafted HTTP requests to external targets by substituting a FUZZ keyword with wordlist entries, which constitutes external operation execution. It runs on a remote Kali Linux host via SSH, meaning it can trigger large-scale fuzzing attacks against web applications.
From the tool's definition 'Fuzzes keyword in URLs, headers, or POST data with wordlist entries' and 'Executes on remote Kali host via SSH'
Attacks that exploit this kind of access
Fuzzing mode - replaces the FUZZ keyword in URLs, headers, or POST data with wordlist entries. Useful for parameter discovery and testing. Executes on remote Kali host via SSH. It is categorised as a Execute tool in the Gobuster MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Gobuster MCP server in PolicyLayer and add a rule for gobuster_fuzz: 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 Gobuster. Nothing to install.
gobuster_fuzz 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 gobuster_fuzz 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 gobuster_fuzz. 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.
gobuster_fuzz is provided by the Gobuster MCP server (schwarztim/sec-gobuster-mcp). 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 →