check_worker_status
AI agents call check_worker_status to retrieve information from Reservation Platform MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name suggests a read-only operation that queries the status of workers or background processes. No evidence of side effects, data modification, or irreversible operations. The empty description lowers confidence slightly, but the naming pattern ('check_*') is consistent with read operations elsewhere on this server (e.g., 'check_duplicate_reservations', 'check_time_slot').
From the tool's definition Tool name 'check_worker_status' indicates a status query operation. Description is empty, limiting direct evidence.
Attacks that exploit this kind of access
check_worker_status. It is categorised as a Read tool in the Reservation Platform MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Reservation Platform MCP Server 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 Reservation Platform MCP Server. Nothing to install.
check_worker_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_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.
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.
check_worker_status is provided by the Reservation Platform MCP Server MCP server (pak3430/reservation-platform-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →