AI agents call crawl_server_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 only retrieves status information about the crawl server. It has no side effects, does not modify data, execute code, delete anything, or move money. It is purely informational and falls squarely into the Read category with low severity since server status queries pose minimal risk.
From the tool's definition Tool name 'crawl_server_status' and description '获取服务器状态信息' (get server status information) indicates a query operation that retrieves status data without modifying or executing anything.
Documented attack patterns abuse exactly the kind of access crawl_server_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_server_status:
{
"version": "1",
"default": "deny",
"tools": {
"crawl_server_status": {}
}
}crawl_server_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_server_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_server_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_server_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_server_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_server_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.