hakrawler_crawl
A execute tool on the Pengstrike MCP server.
This record as markdown: /tools/pengstrike-mcp/hakrawler-crawl.md
What hakrawler_crawl does on Pengstrike
AI agents invoke hakrawler_crawl to trigger actions in Pengstrike. 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 hakrawler_crawl is rated High
Hakrawler is a fast web crawler used in penetration testing and reconnaissance to enumerate URLs, endpoints, and assets of a target. Despite the empty description, the tool name strongly implies it executes an active crawl against an external target, which constitutes an external operation whose effects depend on arguments. In a security recon context, this could be used to probe targets without authorization.
From the tool's definition Tool name 'hakrawler_crawl' combined with server context (browser-native AI recon console, MCP security tools). 'hakrawler' is a well-known web crawler/spider tool used in security reconnaissance.
Attacks that exploit this kind of access
The rule that runs hakrawler_crawl safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Pengstrike, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For hakrawler_crawl, this is the rule to start with:
hakrawler_crawl 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 Pengstrike, apply this rule, and every hakrawler_crawl call is checked against it from then on.
Questions about hakrawler_crawl
hakrawler_crawl is a execute tool on the Pengstrike MCP server. It is categorised as a Execute tool in the Pengstrike MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Pengstrike MCP server in PolicyLayer and add a rule for hakrawler_crawl: 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 Pengstrike. Nothing to install.
hakrawler_crawl 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 hakrawler_crawl 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 hakrawler_crawl. 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.
hakrawler_crawl is provided by the Pengstrike MCP server (wangqiongpeng/pengstrike-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Pengstrike, and thousands of servers like it.
Across the catalogue