Check the status of a crawl job. Args: job_id: The ID of the crawl job to check Returns: The current status of the crawl job
AI agents call check_crawl_status to retrieve information from ReActMCP Web Search without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and returns information about an already-initiated crawl job's current state. It is a pure query operation with no side effects, modifications to data, code execution, or destructive actions. It fits squarely in the Read category as a status-checking/monitoring function.
From the tool's definition Tool name 'check_crawl_status' and description indicate it 'Check[s] the status of a crawl job' by querying an existing job's state. The function takes only a job_id parameter and returns status information without modifying, executing, or deleting anything.
Documented attack patterns abuse exactly the kind of access check_crawl_status gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and ReActMCP Web Search, and nothing reaches the server without passing your rules. This is the rule we recommend for check_crawl_status:
{
"version": "1",
"default": "deny",
"tools": {
"check_crawl_status": {}
}
}check_crawl_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.
Check the status of a crawl job. Args: job_id: The ID of the crawl job to check Returns: The current status of the crawl job. It is categorised as a Read tool in the ReActMCP Web Search MCP Server, which means it retrieves data without modifying state.
Register the ReActMCP Web Search MCP server in PolicyLayer and add a rule for check_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 ReActMCP Web Search. Nothing to install.
check_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 check_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 check_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.
check_crawl_status is provided by the ReActMCP Web Search MCP server (mshojaei77/reactmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from ReActMCP Web Search, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
7 ReActMCP Web Search tools catalogued and risk-classified — across an index of 43,000+ MCP servers.