dirbScan
AI agents invoke dirbScan to trigger actions in Linux Network Scanner 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.
'dirb' is a Linux tool that performs active directory/file brute-forcing against web servers by sending numerous HTTP requests. This constitutes execution of an external network operation against target systems.
From the tool's definition Tool name 'dirbScan' on a server with sibling tools like 'exploitScan', 'ftpBruteForce', 'gobusterScan', 'aircrackScan' — all offensive security tools. 'dirb' is a well-known web content scanner/directory brute-forcer that actively probes web servers.
Attacks that exploit this kind of access
dirbScan. It is categorised as a Execute tool in the Linux Network Scanner MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Linux Network Scanner MCP Server MCP server in PolicyLayer and add a rule for dirbScan: 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 Linux Network Scanner MCP Server. Nothing to install.
dirbScan 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 dirbScan 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 dirbScan. 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.
dirbScan is provided by the Linux Network Scanner MCP Server MCP server (nibesh0/netsecmcp). 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 →