Fast directory and file brute forcing using Gobuster.
AI agents invoke gobuster_directory_scan to trigger actions in ikaliMCP 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.
Gobuster performs active brute-force enumeration against a target web server, sending large volumes of HTTP requests to discover hidden directories and files. This is an active offensive reconnaissance tool that triggers external operations against a target system.
From the tool's definition Fast directory and file brute forcing using Gobuster
Attacks that exploit this kind of access
Fast directory and file brute forcing using Gobuster. It is categorised as a Execute tool in the ikaliMCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the ikaliMCP Server MCP server in PolicyLayer and add a rule for gobuster_directory_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 ikaliMCP Server. Nothing to install.
gobuster_directory_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 gobuster_directory_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 gobuster_directory_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.
gobuster_directory_scan is provided by the ikaliMCP Server MCP server (whobcode/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 →