Directory/file enumeration using gobuster
AI agents invoke gobuster_dir to trigger actions in Kali Linux MCP 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 actively sends HTTP requests to enumerate directories and files on target web servers. This constitutes execution of an external operation against a target system. While it does not modify data, it performs active reconnaissance that can be intrusive, potentially triggering security alerts or causing load on target systems.
From the tool's definition Directory/file enumeration using gobuster — actively scans and probes web servers to discover hidden directories and files
Attacks that exploit this kind of access
Directory/file enumeration using gobuster. It is categorised as a Execute tool in the Kali Linux MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Kali Linux MCP Server MCP server in PolicyLayer and add a rule for gobuster_dir: 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 Linux MCP Server. Nothing to install.
gobuster_dir 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_dir 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_dir. 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_dir is provided by the Kali Linux MCP Server MCP server (pellax/kalimcp). 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 →