# get_status

Check the processing status and progress of a process_url job.

Agent View of the PolicyLayer registry record for `get_status`. HTML page: https://policylayer.com/tools/destinyfrancis-openclaw-knowledge-distiller/get-status

## Facts

- Tool: `get_status`
- Server: Open CLAW Knowledge Distiller (`destinyfrancis/openclaw-knowledge-distiller`) — https://policylayer.com/tools/destinyfrancis-openclaw-knowledge-distiller.md
- Homepage: https://github.com/destinyfrancis/openclaw-knowledge-distiller
- 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_status",
    "arguments": {}
  }
}
```

## Why get_status is rated Low

This tool retrieves and reports the current status of an existing background job. It has no side effects—it only reads state information. This is a classic Read operation with minimal risk, as it cannot modify data, execute code, delete resources, or trigger external operations based on variable inputs.

From the tool's own definition: "Tool name 'get_status' and description 'Check the processing status and progress of a process_url job' indicate a query operation that retrieves job status information without modifying, executing, or deleting any data."

## Use case

AI agents call get_status to retrieve information from Open CLAW Knowledge Distiller 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 Open CLAW Knowledge Distiller:

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

## Other tools on Open CLAW Knowledge Distiller (6)

- `process_url` — Execute — https://policylayer.com/tools/destinyfrancis-openclaw-knowledge-distiller/process-url.md
- `transcribe_url` — Execute — https://policylayer.com/tools/destinyfrancis-openclaw-knowledge-distiller/transcribe-url.md
- `get_result` — Read — https://policylayer.com/tools/destinyfrancis-openclaw-knowledge-distiller/get-result.md
- `list_jobs` — Read — https://policylayer.com/tools/destinyfrancis-openclaw-knowledge-distiller/list-jobs.md
- `list_styles` — Read — https://policylayer.com/tools/destinyfrancis-openclaw-knowledge-distiller/list-styles.md
- `configure` — Write — https://policylayer.com/tools/destinyfrancis-openclaw-knowledge-distiller/configure.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=destinyfrancis-openclaw-knowledge-distiller · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/destinyfrancis-openclaw-knowledge-distiller