crow_job_status

Check a delegated background job by its job id (returned by crow_delegate). Returns its

SERVERCrow SOURCEkh0pper/crow

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/kh0pper-crow/crow-job-status.md

WHAT IT DOES

What crow_job_status does on Crow

AI agents call crow_job_status to retrieve information from Crow without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why crow_job_status is rated Low

This tool performs a status query on an existing background job. It retrieves information about a job's state without creating, modifying, deleting, or executing any operations. The action is purely informational and has no side effects beyond returning status data.

From the tool's definition Tool description states 'Check a delegated background job by its job id' - the verb 'Check' and the read-only nature of querying job status indicates retrieval without modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs crow_job_status safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Crow, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For crow_job_status, this is the rule to start with:

crow_job_status Allowed

crow_job_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "crow_job_status": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Crow, apply this rule, and every crow_job_status call is checked against it from then on.

FAQ

Questions about crow_job_status

What does the crow_job_status tool do? +

Check a delegated background job by its job id (returned by crow_delegate). Returns its. It is categorised as a Read tool in the Crow MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on crow_job_status? +

Register the Crow MCP server in PolicyLayer and add a rule for crow_job_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.

What risk level is crow_job_status? +

crow_job_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit crow_job_status? +

Yes. Add a rate_limit block to the crow_job_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.

How do I block crow_job_status completely? +

Set action: deny in the PolicyLayer policy for crow_job_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.

What MCP server provides crow_job_status? +

crow_job_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.

KEEP EXPLORING

More on Crow, and thousands of servers like it.

This server

All 602 Crow tools →

Across the catalogue

editor_status on 010 Editor → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →