AI agents invoke run_gobuster_scan to trigger actions in pentestMCP. 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 a reconnaissance tool that performs brute-force attacks against web servers and DNS infrastructure. This is an Execute action: it triggers external security operations (network scanning and enumeration) whose effects depend on provided arguments (target, wordlists, scan parameters). While not destructive itself, it performs active reconnaissance that could disrupt services or trigger security alerts.
From the tool's definition Tool name 'run_gobuster_scan' indicates execution of Gobuster, a web directory/DNS brute-forcing utility. Server description confirms it exposes 'over 20 standard penetration testing utilities' as 'callable tools'.
Documented attack patterns abuse exactly the kind of access run_gobuster_scan gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and pentestMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for run_gobuster_scan:
{
"version": "1",
"default": "deny",
"tools": {
"run_gobuster_scan": {
"limits": [
{
"counter": "run_gobuster_scan_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}run_gobuster_scan stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
run_gobuster_scan. It is categorised as a Execute tool in the pentestMCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the pentest MCP server in PolicyLayer and add a rule for run_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 pentestMCP. Nothing to install.
run_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 run_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 run_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.
run_gobuster_scan is provided by the pentest MCP server (ramkansal/pentestmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 36 pentestMCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
36 pentestMCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.