Check the progress of a crawl job. Returns status, pages crawled, and duration.
AI agents call crawl_status to retrieve information from UnWeb MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only reads and returns status information about an existing crawl job. It has no side effects—it neither creates, modifies, deletes, executes, nor commits financial obligations. The operation is a passive query of job progress metadata.
From the tool's definition Tool name 'crawl_status' and description 'Check the progress of a crawl job. Returns status, pages crawled, and duration' indicate a query/monitoring operation that retrieves information about an ongoing process without modifying or executing anything.
Attacks that exploit this kind of access
Check the progress of a crawl job. Returns status, pages crawled, and duration. It is categorised as a Read tool in the UnWeb MCP Server MCP Server, which means it retrieves data without modifying state.
Register the UnWeb MCP Server MCP server in PolicyLayer and add a rule for crawl_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 UnWeb MCP Server. Nothing to install.
crawl_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_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_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_status is provided by the UnWeb MCP Server MCP server (mbsoft-systems/unweb-mcp). 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 →