Execute Dirb web content scanner.
AI agents invoke dirb_scan to trigger actions in MCP Kali 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.
dirb is an active web content scanner that sends HTTP requests to enumerate directories and files on web servers. It executes external commands against target systems, which constitutes active reconnaissance. In a penetration testing context, misuse could target unauthorized systems.
From the tool's definition 'Execute Dirb web content scanner' - runs an active web directory/content scanning tool against target web servers
Attacks that exploit this kind of access
Execute Dirb web content scanner. It is categorised as a Execute tool in the MCP Kali Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MCP Kali 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 MCP Kali Server. Nothing to install.
dirb_scan is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
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.
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.
dirb_scan is provided by the MCP Kali Server MCP server (wh0am123/mcp-kali-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.