Check status / retrieve the result of an orchestration job by its job id. Returns running, completed (with summary), or failed.
AI agents call crow_orchestrate_status to retrieve information from Crow without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a pure read operation that queries the state of an existing orchestration job and returns its status and summary. No data is created, modified, deleted, or executed as a side effect. The retrieval of results is informational only, making this a low-severity Read category tool.
From the tool's definition Tool description explicitly states it 'Check[s] status / retrieve[s] the result' of orchestration jobs, returning status values (running, completed, failed) without modifying or deleting data.
Documented attack patterns abuse exactly the kind of access crow_orchestrate_status gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Crow, and nothing reaches the server without passing your rules. This is the rule we recommend for crow_orchestrate_status:
{
"version": "1",
"default": "deny",
"tools": {
"crow_orchestrate_status": {}
}
}crow_orchestrate_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 status / retrieve the result of an orchestration job by its job id. Returns running, completed (with summary), or failed. It is categorised as a Read tool in the Crow MCP Server, which means it retrieves data without modifying state.
Register the Crow MCP server in PolicyLayer and add a rule for crow_orchestrate_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 Crow. Nothing to install.
crow_orchestrate_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 crow_orchestrate_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 crow_orchestrate_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.
crow_orchestrate_status is provided by the Crow MCP server (kh0pper/crow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Crow, 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.
576 Crow tools catalogued and risk-classified — across an index of 43,000+ MCP servers.