dirb_scan · Bug Bounty MCP Server MCP: Risk & Policy

WHAT IT DOES

What dirb_scan does on Bug Bounty MCP Server

AI agents invoke dirb_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 dirb_scan needs a policy

DIRB is a well-known active reconnaissance tool that sends HTTP requests to enumerate directories and files on a web server. Running it constitutes an external operation against a target system. The description is empty, so confidence is reduced, but the tool name and server context make this classification highly probable. Severity is high because misuse could constitute unauthorized scanning of systems.

From the tool's definition Tool name 'dirb_scan' strongly implies execution of the DIRB web content scanner, a directory brute-forcing tool that actively probes target web servers. The server description references reconnaissance and vulnerability testing workflows.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

dirb_scan Rate-limited

dirb_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": {
    "dirb_scan": {
      "limits": [
        {
          "counter": "dirb_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 dirb_scan

What does the dirb_scan tool do? +

dirb_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 dirb_scan? +

Register the Bug Bounty MCP Server MCP server in PolicyLayer and add a rule for dirb_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 dirb_scan? +

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

Can I rate-limit dirb_scan? +

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

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

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