gobuster_scan
AI agents invoke gobuster_scan to trigger actions in MCP Kali 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 executes active network scanning and brute-force enumeration against target systems. Even though the description is empty, the tool name and server context (Kali Linux pentesting, sibling tools include Metasploit, Hydra, SQLMap) make it clear this runs an offensive scanning operation against external targets. This is classified as Execute because it triggers external network operations.
From the tool's definition Tool name 'gobuster_scan' on a Kali Linux penetration testing server alongside tools like metasploit_run, hydra_attack, sqlmap_scan, and execute_command. Gobuster is a directory/DNS/vhost brute-forcing tool used in offensive security.
Attacks that exploit this kind of access
gobuster_scan. It is categorised as a Execute tool in the MCP Kali Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MCP Kali Server MCP server in PolicyLayer and add a rule for gobuster_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 MCP Kali Server. Nothing to install.
gobuster_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_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_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_scan is provided by the MCP Kali Server MCP server (wh0am123/mcp-kali-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.