dirsearch_scan · Bug Bounty MCP Server MCP: Risk & Policy

WHAT IT DOES

What dirsearch_scan does on Bug Bounty MCP Server

AI agents invoke dirsearch_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 dirsearch_scan needs a policy

This tool runs an external scanning utility (Dirsearch) against a target system to discover directories and files. It triggers active network operations whose effects depend on the target argument. It is part of a bug bounty/offensive security server, meaning it performs active reconnaissance against external systems.

From the tool's definition 'Run Dirsearch for advanced directory and file discovery' — actively executes the Dirsearch tool against a target

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

dirsearch_scan Rate-limited

dirsearch_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": {
    "dirsearch_scan": {
      "limits": [
        {
          "counter": "dirsearch_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 dirsearch_scan

What does the dirsearch_scan tool do? +

Run Dirsearch for advanced directory and file discovery with logging. 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 dirsearch_scan? +

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

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

Can I rate-limit dirsearch_scan? +

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

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

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