# check_order_status

Check the status of the most recent order. Requires a session key from a previous tool call.

Agent View of the PolicyLayer registry record for `check_order_status`. HTML page: https://policylayer.com/tools/com-gitsim-chat/check-order-status

## Facts

- Tool: `check_order_status`
- Server: Gitsim Chat (`https://chat.gitsim.com/api/mcp`) — https://policylayer.com/tools/com-gitsim-chat.md
- Homepage: https://github.com/https://chat.gitsim.com/api/mcp
- Risk category: Read (Low risk)
- Registry record: grade C, identity unverified
- Server auth posture: open
- Server rate-limited: no
- Parameters: 1 (1 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `session_key` | string | yes | Session key from a previous tool call |

Parameters from the server's own tool schema.

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

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "check_order_status",
    "arguments": {
      "session_key": "<session_key>"
    }
  }
}
```

## Why check_order_status is rated Low

This tool queries existing order information without side effects. It is a straightforward information retrieval operation analogous to 'get' or 'fetch'. While the eSIM context involves financial transactions on the server, this specific tool only reads order status rather than committing financial obligations or modifying state. Therefore, it falls under the Read category with low severity.

From the tool's own definition: "The tool 'check_order_status' retrieves the status of an order. The verb 'check' and the action of retrieving status information (no modification, deletion, or execution) indicate a read-only operation."

## Use case

AI agents call check_order_status to retrieve information from Gitsim Chat 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 Gitsim Chat:

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

## Other tools on Gitsim Chat (8)

- `buy_topup` — Financial — https://policylayer.com/tools/com-gitsim-chat/buy-topup.md
- `create_order` — Financial — https://policylayer.com/tools/com-gitsim-chat/create-order.md
- `check_data_balance` — Read — https://policylayer.com/tools/com-gitsim-chat/check-data-balance.md
- `get_business_context` — Read — https://policylayer.com/tools/com-gitsim-chat/get-business-context.md
- `get_package` — Read — https://policylayer.com/tools/com-gitsim-chat/get-package.md
- `list_esims` — Read — https://policylayer.com/tools/com-gitsim-chat/list-esims.md
- `search_packages` — Read — https://policylayer.com/tools/com-gitsim-chat/search-packages.md
- `search_topup_packages` — Read — https://policylayer.com/tools/com-gitsim-chat/search-topup-packages.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=com-gitsim-chat · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-gitsim-chat