Check lifecycle status (running|completed|failed|canceled|orphaned) of a gateway async or deferred-sync job by jobId.
AI agents call llm_job_status to retrieve information from LLM CLI Gateway without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only queries the state of existing async jobs and returns status metadata. It has no side effects, cannot modify job state, trigger execution, delete data, or affect finances. It is a straightforward read operation with minimal blast radius if misused by an AI agent.
From the tool's definition Tool description states 'Check lifecycle status ... by jobId' — a pure query operation that retrieves status information without modifying, deleting, or executing external operations.
Documented attack patterns abuse exactly the kind of access llm_job_status gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and LLM CLI Gateway, and nothing reaches the server without passing your rules. This is the rule we recommend for llm_job_status:
{
"version": "1",
"default": "deny",
"tools": {
"llm_job_status": {}
}
}llm_job_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 lifecycle status (running|completed|failed|canceled|orphaned) of a gateway async or deferred-sync job by jobId. It is categorised as a Read tool in the LLM CLI Gateway MCP Server, which means it retrieves data without modifying state.
Register the LLM CLI Gateway MCP server in PolicyLayer and add a rule for llm_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 LLM CLI Gateway. Nothing to install.
llm_job_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 llm_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.
Set action: deny in the PolicyLayer policy for llm_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.
llm_job_status is provided by the LLM CLI Gateway MCP server (llm-cli-gateway). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from LLM CLI Gateway, 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.
46 LLM CLI Gateway tools catalogued and risk-classified — across an index of 43,000+ MCP servers.