check_worker_status

A read tool on the Agent Jail MCP server.

SERVERAgent Jail SOURCEidiscoord13-sketch/agent-jail-mcp

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/agent-jail-mcp/check-worker-status.md

WHAT IT DOES

What check_worker_status does on Agent Jail

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

RISK

Why check_worker_status is rated Low

Based on the tool name alone, 'check_worker_status' appears to retrieve or query the status of a worker resource, which is a read-only operation with no side effects. The empty description reduces confidence slightly, but the semantic meaning of 'check' and 'status' strongly suggests a non-destructive query. No evidence of writes, execution, deletion, or financial operations.

From the tool's definition Tool name 'check_worker_status' indicates a status query operation. The description is empty, but the naming convention suggests information retrieval without modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs check_worker_status safely

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

check_worker_status Allowed

check_worker_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": {
    "check_worker_status": {}
  }
}

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

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

FAQ

Questions about check_worker_status

What does the check_worker_status tool do? +

check_worker_status is a read tool on the Agent Jail MCP server. It is categorised as a Read tool in the Agent Jail MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on check_worker_status? +

Register the Agent Jail MCP server in PolicyLayer and add a rule for check_worker_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 Agent Jail. Nothing to install.

What risk level is check_worker_status? +

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

Can I rate-limit check_worker_status? +

Yes. Add a rate_limit block to the check_worker_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 check_worker_status completely? +

Set action: deny in the PolicyLayer policy for check_worker_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 check_worker_status? +

check_worker_status is provided by the Agent Jail MCP server (idiscoord13-sketch/agent-jail-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Agent Jail, and thousands of servers like it.

This server

All 35 Agent Jail tools →

Across the catalogue

claude_git_status on Claude Bridge →get_task_status on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

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