hakrawler_crawl
AI agents invoke hakrawler_crawl to trigger actions in Bug Bounty 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.
Hakrawler is a well-known web crawling/reconnaissance tool used in bug bounty hunting. The tool likely executes the hakrawler binary against a target URL, performing active web crawling which constitutes an external operation. The empty description lowers confidence, but the tool name and server context strongly suggest active execution against external targets.
From the tool's definition Tool name 'hakrawler_crawl' suggests running the hakrawler web crawler tool against a target; server description mentions reconnaissance and vulnerability testing workflows
Attacks that exploit this kind of access
hakrawler_crawl. It is categorised as a Execute tool in the Bug Bounty MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Bug Bounty MCP Server 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 Bug Bounty MCP Server. 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 Bug Bounty MCP Server MCP server (slanycukr/bugbounty-mcp-server). 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 →