feroxbuster_stop · Feroxbuster MCP: Risk & Policy

WHAT IT DOES

What feroxbuster_stop does on Feroxbuster

AI agents invoke feroxbuster_stop to trigger actions in Feroxbuster. 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 feroxbuster_stop needs a policy

Stopping a running process is an Execute category action—it triggers an external operation with effects that depend on what scan was running. While terminating a scan is reversible (unlike Destructive actions which cannot be undone), it is not a Read operation (retrieves no data), Write operation (creates/modifies no persistent data), or Financial operation.

From the tool's definition Tool enables stopping a running feroxbuster scan, which is an external operation that terminates a process on a remote system via SSH.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

feroxbuster_stop Rate-limited

feroxbuster_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": {
    "feroxbuster_stop": {
      "limits": [
        {
          "counter": "feroxbuster_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 Feroxbuster, so you can run agents against it safely.

FAQ

Questions about feroxbuster_stop

What does the feroxbuster_stop tool do? +

Stop a running feroxbuster scan. It is categorised as a Execute tool in the Feroxbuster MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on feroxbuster_stop? +

Register the Feroxbuster MCP server in PolicyLayer and add a rule for feroxbuster_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 Feroxbuster. Nothing to install.

What risk level is feroxbuster_stop? +

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

Can I rate-limit feroxbuster_stop? +

Yes. Add a rate_limit block to the feroxbuster_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 feroxbuster_stop completely? +

Set action: deny in the PolicyLayer policy for feroxbuster_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 feroxbuster_stop? +

feroxbuster_stop is provided by the Feroxbuster MCP server (schwarztim/sec-feroxbuster-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.