gobuster_scan
AI agents invoke gobuster_scan to trigger actions in Bug Bounty 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 is an active scanning tool that brute-forces URLs, DNS subdomains, and virtual hosts against external targets. Even though the description is empty, the tool name and server context strongly indicate it executes network-level scanning operations against target systems.
From the tool's definition Tool name 'gobuster_scan' — gobuster is a well-known directory/DNS/vhost brute-forcing tool used in security reconnaissance; part of a Bug Bounty MCP Server with sibling tools like amass_scan, arjun_parameter_discovery, and vulnerability hunting workflows
Attacks that exploit this kind of access
gobuster_scan. It is categorised as a Execute tool in the Bug Bounty MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Bug Bounty MCP 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 Bug Bounty MCP 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 Bug Bounty MCP Server MCP server (slanycukr/bugbounty-mcp-server). 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 →