Perform directory brute force scan using Dirb
AI agents invoke dirb_scan to trigger actions in Echo 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.
This tool executes a Dirb directory brute-force scan against a target, which is an active external network operation. It can be used to enumerate hidden directories and files on web servers, which is a reconnaissance technique. The tool triggers an external operation (network scanning) whose effects depend on the target argument.
From the tool's definition Perform directory brute force scan using Dirb
Attacks that exploit this kind of access
Perform directory brute force scan using Dirb. It is categorised as a Execute tool in the Echo MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Echo 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 Echo MCP 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 Echo MCP Server MCP server (somacaru/mcp_setup). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →