# get_task_status

Check the current status of a task.

Agent View of the PolicyLayer registry record for `get_task_status`. HTML page: https://policylayer.com/tools/0rcanetworkalgorand-dojo-mcp/get-task-status

## Facts

- Tool: `get_task_status`
- Server: 0rca Dojo MCP Server (`0rcanetworkalgorand/dojo_mcp`) — https://policylayer.com/tools/0rcanetworkalgorand-dojo-mcp.md
- Homepage: https://github.com/0rcanetworkalgorand/dojo_mcp
- Risk category: Read (Low risk)
- Registry record: grade B, 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": "get_task_status",
    "arguments": {}
  }
}
```

## Why get_task_status is rated Low

This tool retrieves the status of an existing task, which is a read-only operation with no side effects. It does not create, modify, delete data, nor does it execute code or trigger financial transactions. The blast radius of misuse is minimal—an agent could only view task statuses, not alter them.

From the tool's own definition: "Tool name 'get_task_status' and description 'Check the current status of a task' indicate a query operation that retrieves status information without modifying, deleting, or executing external operations."

## Use case

AI agents call get_task_status to retrieve information from 0rca Dojo MCP Server 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 0rca Dojo MCP Server:

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

## Other tools on 0rca Dojo MCP Server (5)

- `get_agent` — Read — https://policylayer.com/tools/0rcanetworkalgorand-dojo-mcp/get-agent.md
- `list_agents` — Read — https://policylayer.com/tools/0rcanetworkalgorand-dojo-mcp/list-agents.md
- `list_tasks` — Read — https://policylayer.com/tools/0rcanetworkalgorand-dojo-mcp/list-tasks.md
- `match_agent` — Read — https://policylayer.com/tools/0rcanetworkalgorand-dojo-mcp/match-agent.md
- `create_task` — Write — https://policylayer.com/tools/0rcanetworkalgorand-dojo-mcp/create-task.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=0rcanetworkalgorand-dojo-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/0rcanetworkalgorand-dojo-mcp