dirb_directory_scan · ikaliMCP Server MCP: Risk & Policy

WHAT IT DOES

What dirb_directory_scan does on ikaliMCP Server

AI agents invoke dirb_directory_scan to trigger actions in ikaliMCP 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_directory_scan needs a policy

DIRB performs active brute-force scanning against a target web server to enumerate hidden directories and files. This constitutes execution of an external offensive security tool that sends large volumes of HTTP requests to a target system. While it is read-like in intent (discovery), it actively hammers a remote server and is part of a penetration testing toolkit alongside sqlmap, hydra, and nikto.

From the tool's definition Directory and file brute forcing using DIRB - discovers hidden directories and files

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

dirb_directory_scan Rate-limited

dirb_directory_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_directory_scan": {
      "limits": [
        {
          "counter": "dirb_directory_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 ikaliMCP Server, so you can run agents against it safely.

FAQ

Questions about dirb_directory_scan

What does the dirb_directory_scan tool do? +

Directory and file brute forcing using DIRB - discovers hidden directories and files. It is categorised as a Execute tool in the ikaliMCP 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_directory_scan? +

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

What risk level is dirb_directory_scan? +

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

Can I rate-limit dirb_directory_scan? +

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

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

dirb_directory_scan is provided by the ikaliMCP Server MCP server (whobcode/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.