run_crunch
A execute tool on the Pentester- MCP server.
This record as markdown: /tools/halilkirazkaya-pentester-mcp/run-crunch.md
What run_crunch does on Pentester-MCP
AI agents invoke run_crunch 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_crunch is rated High
Crunch is a utility that generates custom wordlists for password cracking and brute-force attacks. The 'run_' prefix indicates the tool executes this external program. This falls under Execute category as it triggers an external operation whose security impact depends on how the AI agent configures the wordlist parameters (length, character sets, output size).
From the tool's definition Tool belongs to Pentester-MCP server that enables 'autonomous execution of over 200 open-source penetration testing tools including reconnaissance, web exploitation, and brute-forcing.' The tool name 'run_crunch' indicates execution of crunch (a wordlist…
Attacks that exploit this kind of access
The rule that runs run_crunch safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Pentester-MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For run_crunch, this is the rule to start with:
run_crunch 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Pentester-MCP, apply this rule, and every run_crunch call is checked against it from then on.
Questions about run_crunch
run_crunch 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.
Register the Pentester MCP server in PolicyLayer and add a rule for run_crunch: 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.
run_crunch 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 run_crunch 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 run_crunch. 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.
run_crunch 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.
Across the catalogue