New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

run_dirsearch

A execute tool on the Pentester- MCP server.

SERVERPentester-MCP SOURCEhalilkirazkaya/pentester-mcp
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/halilkirazkaya-pentester-mcp/run-dirsearch.md

What run_dirsearch does on Pentester-MCP

AI agents invoke run_dirsearch to trigger actions in Pentester-MCP. 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 run_dirsearch is rated High

dirsearch executes reconnaissance against a target web application—a core penetration testing operation with tangible side effects (network traffic, resource consumption, potential triggering of security controls). It is not merely a query tool (Read), as it actively scans and probes systems.

From the tool's definition Tool named 'run_dirsearch' on a penetration testing server (Pentester-MCP) described as executing '200+ open-source penetration testing tools'; dirsearch is a directory/file enumeration scanner that performs HTTP requests to discover hidden web endpoints.

Questions about run_dirsearch

What does the run_dirsearch tool do? +

run_dirsearch is a execute tool on the Pentester MCP server. It is categorised as a Execute tool in the Pentester-MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on run_dirsearch? +

Register the Pentester MCP server in PolicyLayer and add a rule for run_dirsearch: 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 Pentester-MCP. Nothing to install.

What risk level is run_dirsearch? +

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

Can I rate-limit run_dirsearch? +

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

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

run_dirsearch is provided by the Pentester MCP server (halilkirazkaya/pentester-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Pentester, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Pentester's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.