gobuster_stop · Gobuster MCP: Risk & Policy

WHAT IT DOES

What gobuster_stop does on Gobuster

AI agents invoke gobuster_stop 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.

WHY IT NEEDS A POLICY

Why gobuster_stop needs a policy

This tool triggers termination of a background scan process. While stopping a scan is generally safe and reversible (the scan can be restarted), it still constitutes execution of a control command against an external system (the Kali Linux host). The tool's effect depends on runtime arguments (which scan ID to stop), fitting the Execute category rather than Read.

From the tool's definition Tool performs an action on a running process ('Stop a running asynchronous gobuster scan'), terminating an external operation whose effects depend on which scan is targeted.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

gobuster_stop Rate-limited

gobuster_stop 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "gobuster_stop": {
      "limits": [
        {
          "counter": "gobuster_stop_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Gobuster, so you can run agents against it safely.

FAQ

Questions about gobuster_stop

What does the gobuster_stop tool do? +

Stop a running asynchronous gobuster scan. 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.

How do I enforce a policy on gobuster_stop? +

Register the Gobuster MCP server in PolicyLayer and add a rule for gobuster_stop: 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.

What risk level is gobuster_stop? +

gobuster_stop is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit gobuster_stop? +

Yes. Add a rate_limit block to the gobuster_stop 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.

How do I block gobuster_stop completely? +

Set action: deny in the PolicyLayer policy for gobuster_stop. 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.

What MCP server provides gobuster_stop? +

gobuster_stop 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.