# check_worker_status

A read tool on the Cryptosense MCP server.

Agent View of the PolicyLayer registry record for `check_worker_status`. HTML page: https://policylayer.com/tools/josephibra-cryptosense-mcp/check-worker-status

## Facts

- Tool: `check_worker_status`
- Server: Cryptosense (`josephibra/cryptosense-mcp`) — https://policylayer.com/tools/josephibra-cryptosense-mcp.md
- Homepage: https://github.com/josephibra/cryptosense-mcp
- Risk category: Read (Low risk)
- Registry record: grade D, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "check_worker_status",
    "arguments": {}
  }
}
```

## Why check_worker_status is rated Low

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 own 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."

## Use case

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

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Cryptosense:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "check_worker_status": {}
  }
}
```

## Other tools on Cryptosense (35)

- `run_query` — Execute — https://policylayer.com/tools/josephibra-cryptosense-mcp/run-query.md
- `async_tool` — Other — https://policylayer.com/tools/josephibra-cryptosense-mcp/async-tool.md
- `custom_name` — Other — https://policylayer.com/tools/josephibra-cryptosense-mcp/custom-name.md
- `greeting` — Other — https://policylayer.com/tools/josephibra-cryptosense-mcp/greeting.md
- `log_progress` — Other — https://policylayer.com/tools/josephibra-cryptosense-mcp/log-progress.md
- `multiply` — Other — https://policylayer.com/tools/josephibra-cryptosense-mcp/multiply.md
- `my_task` — Other — https://policylayer.com/tools/josephibra-cryptosense-mcp/my-task.md
- `my_tool` — Other — https://policylayer.com/tools/josephibra-cryptosense-mcp/my-tool.md
- `tool_with_context` — Other — https://policylayer.com/tools/josephibra-cryptosense-mcp/tool-with-context.md
- `compare` — Read — https://policylayer.com/tools/josephibra-cryptosense-mcp/compare.md
- `echo_tool` — Read — https://policylayer.com/tools/josephibra-cryptosense-mcp/echo-tool.md
- `get_auth_type` — Read — https://policylayer.com/tools/josephibra-cryptosense-mcp/get-auth-type.md
- `get_client_ip` — Read — https://policylayer.com/tools/josephibra-cryptosense-mcp/get-client-ip.md
- `get_info` — Read — https://policylayer.com/tools/josephibra-cryptosense-mcp/get-info.md
- `get_my_emails` — Read — https://policylayer.com/tools/josephibra-cryptosense-mcp/get-my-emails.md
- `get_user_id` — Read — https://policylayer.com/tools/josephibra-cryptosense-mcp/get-user-id.md
- `greet` — Read — https://policylayer.com/tools/josephibra-cryptosense-mcp/greet.md
- `introspect` — Read — https://policylayer.com/tools/josephibra-cryptosense-mcp/introspect.md
- `list_files` — Read — https://policylayer.com/tools/josephibra-cryptosense-mcp/list-files.md
- `long_running_task` — Read — https://policylayer.com/tools/josephibra-cryptosense-mcp/long-running-task.md
- `market_overview` — Read — https://policylayer.com/tools/josephibra-cryptosense-mcp/market-overview.md
- `portfolio_value` — Read — https://policylayer.com/tools/josephibra-cryptosense-mcp/portfolio-value.md
- `price` — Read — https://policylayer.com/tools/josephibra-cryptosense-mcp/price.md
- `read_file` — Read — https://policylayer.com/tools/josephibra-cryptosense-mcp/read-file.md
- `top_coins` — Read — https://policylayer.com/tools/josephibra-cryptosense-mcp/top-coins.md
- `trending` — Read — https://policylayer.com/tools/josephibra-cryptosense-mcp/trending.md
- `add` — Write — https://policylayer.com/tools/josephibra-cryptosense-mcp/add.md
- `add_expense` — Write — https://policylayer.com/tools/josephibra-cryptosense-mcp/add-expense.md
- `create_api_key` — Write — https://policylayer.com/tools/josephibra-cryptosense-mcp/create-api-key.md
- `save` — Write — https://policylayer.com/tools/josephibra-cryptosense-mcp/save.md
- …and 5 more: https://policylayer.com/tools/josephibra-cryptosense-mcp.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=josephibra-cryptosense-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/josephibra-cryptosense-mcp