AI agents call crawl_get_status to retrieve information from Crawl without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays status information about ongoing crawl operations. It performs queries and monitoring without modifying, executing, or deleting any data. No side effects or external operations are triggered by calling this tool.
From the tool's definition Tool name 'crawl_get_status' and description indicate a status/progress query function: '查询当前抓取任务的进度和状态' (query current crawl task progress and status), '实时监控抓取进度' (real-time monitor crawl progress), '查看成功失败统计' (view success/failure statistics), '获取详细错误信息'…
Documented attack patterns abuse exactly the kind of access crawl_get_status gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Crawl, and nothing reaches the server without passing your rules. This is the rule we recommend for crawl_get_status:
{
"version": "1",
"default": "deny",
"tools": {
"crawl_get_status": {}
}
}crawl_get_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
📊 [抓取状态查询器] 查询当前抓取任务的进度和状态 - 实时监控抓取进度、查看成功失败统计、获取详细错误信息。. It is categorised as a Read tool in the Crawl MCP Server, which means it retrieves data without modifying state.
Register the Crawl MCP server in PolicyLayer and add a rule for crawl_get_status: 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 Crawl. Nothing to install.
crawl_get_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the crawl_get_status 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 crawl_get_status. 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.
crawl_get_status is provided by the Crawl MCP server (wutongci/crawl-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 4 Crawl tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4 Crawl tools catalogued and risk-classified — across an index of 42,500+ MCP servers.