get_order_status
Customer-facing status, ETA window and next action for an order. Requires the buyer's order token (delivered after payment) — the token is the credential; never guess or enumerate tokens. Never returns address, phone or payment details.
This record as markdown: /tools/com-giftroam-giftroam/get-order-status.md
What get_order_status does on Giftroam
AI agents call get_order_status to retrieve information from Giftroam 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 |
|---|---|---|---|
locale | string | — | Language of the conversation with the user (e.g. he-IL, fr-FR). Localizes content and messages; prices and availability are unaffected. |
order_token | string | Yes | The order token from the buyer's confirmation (GR-XXXXX-…). Never guess tokens. |
Parameters from the server's own tool schema.
Why get_order_status is rated Low
Even though get_order_status only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs get_order_status safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Giftroam, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_order_status, this is the rule to start with:
get_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 Giftroam, apply this rule, and every get_order_status call is checked against it from then on.
Questions about get_order_status
Customer-facing status, ETA window and next action for an order. Requires the buyer's order token (delivered after payment) — the token is the credential; never guess or enumerate tokens. Never returns address, phone or payment details. It is categorised as a Read tool in the Giftroam MCP Server, which means it retrieves data without modifying state.
get_order_status accepts 2 parameters: locale, order_token. Required: order_token. The full parameter table on this page comes from the server's own tool schema.
Register the Giftroam MCP server in PolicyLayer and add a rule for get_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 Giftroam. Nothing to install.
get_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 get_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 get_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.
get_order_status is provided by the Giftroam MCP server (https://mcp.giftroam.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Giftroam, and thousands of servers like it.
This server
Across the catalogue