gobuster_scan
AI agents invoke gobuster_scan to trigger actions in K-MCP: Kali Model Context Protocol 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 scans target systems by brute-forcing directories, DNS subdomains, or virtual hosts, sending large volumes of HTTP/DNS requests to external targets. This constitutes execution of an offensive security tool with significant blast radius if aimed at unauthorized targets. The description is empty, but the tool name and server context strongly indicate active scanning behavior.
From the tool's definition Tool name 'gobuster_scan' on a Kali Linux MCP server designed for penetration testing; sibling tools include dirb_scan, hydra_attack, john_crack, execute_command — all offensive security tools.
Attacks that exploit this kind of access
gobuster_scan. It is categorised as a Execute tool in the K-MCP: Kali Model Context Protocol Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the K-MCP: Kali Model Context Protocol 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 K-MCP: Kali Model Context Protocol 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 K-MCP: Kali Model Context Protocol Server MCP server (stoicmehedi/k-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 →