AI agents invoke gobuster_dns 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 executes gobuster in DNS mode on a remote Kali Linux host via SSH, performing active brute-force enumeration against an external target. It triggers external network operations (DNS queries) whose scope depends on the wordlist and target domain provided.
From the tool's definition 'DNS subdomain enumeration mode - discovers subdomains for a target domain using wordlist-based brute forcing. Executes on remote Kali host via SSH.'
Attacks that exploit this kind of access
DNS subdomain enumeration mode - discovers subdomains for a target domain using wordlist-based brute forcing. 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_dns: 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_dns 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_dns 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_dns. 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_dns 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 →