check_worker_status
AI agents call check_worker_status to retrieve information from Cryptosense without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Despite the empty description lowering confidence, the name 'check_worker_status' indicates a read-only operation that queries system state without modifying data, executing code, or causing side effects. No evidence of destructive, financial, or dangerous execute operations. Categorized as Read with low severity due to lack of descriptive detail.
From the tool's definition Tool named 'check_worker_status' with empty description. The name suggests a status query operation. Within a crypto market intelligence MCP context, this likely retrieves worker/service status information.
Attacks that exploit this kind of access
check_worker_status. It is categorised as a Read tool in the Cryptosense MCP Server, which means it retrieves data without modifying state.
Register the Cryptosense 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 Cryptosense. 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 Cryptosense MCP server (josephibra/cryptosense-mcp). 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 →