feroxbuster_scan · Bug Bounty MCP Server MCP: Risk & Policy

WHAT IT DOES

What feroxbuster_scan does on Bug Bounty MCP Server

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

WHY IT NEEDS A POLICY

Why feroxbuster_scan needs a policy

Feroxbuster is a fast, recursive content discovery tool used in bug bounty and penetration testing contexts. Running it constitutes executing an active scan against an external target, which can trigger security alerts, cause unintended load, or access unauthorized resources. The description is empty, so confidence is reduced slightly, but the tool name is unambiguous in the security tooling ecosystem.

From the tool's definition Tool name 'feroxbuster_scan' — Feroxbuster is a well-known web content discovery/fuzzing tool that actively sends HTTP requests to enumerate directories and files on target web servers. It runs an external security scanning tool against a target.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

feroxbuster_scan Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "feroxbuster_scan": {
      "limits": [
        {
          "counter": "feroxbuster_scan_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 Bug Bounty MCP Server, so you can run agents against it safely.

FAQ

Questions about feroxbuster_scan

What does the feroxbuster_scan tool do? +

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

How do I enforce a policy on feroxbuster_scan? +

Register the Bug Bounty MCP Server MCP server in PolicyLayer and add a rule for feroxbuster_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.

What risk level is feroxbuster_scan? +

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

Can I rate-limit feroxbuster_scan? +

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

How do I block feroxbuster_scan completely? +

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

What MCP server provides feroxbuster_scan? +

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