check_order_status
Check the status of the most recent order. Requires a session key from a previous tool call.
This record as markdown: /tools/com-gitsim-chat/check-order-status.md
What check_order_status does on Gitsim Chat
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.
| Parameter | Type | Required | Description |
|---|---|---|---|
session_key | string | Yes | Session key from a previous tool call |
Parameters from the server's own tool schema.
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 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.
Attacks that exploit this kind of access
The rule that runs check_order_status safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Gitsim Chat, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For check_order_status, this is the rule to start with:
check_order_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Gitsim Chat, apply this rule, and every check_order_status call is checked against it from then on.
Questions about check_order_status
Check the status of the most recent order. Requires a session key from a previous tool call. It is categorised as a Read tool in the Gitsim Chat MCP Server, which means it retrieves data without modifying state.
check_order_status accepts 1 parameter: session_key. Required: session_key. The full parameter table on this page comes from the server's own tool schema.
Register the Gitsim Chat MCP server in PolicyLayer and add a rule for check_order_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 Gitsim Chat. Nothing to install.
check_order_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_order_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_order_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_order_status is provided by the Gitsim Chat MCP server (https://chat.gitsim.com/api/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Gitsim Chat, and thousands of servers like it.
This server
Across the catalogue