list_my_orders
The signed-in user's GiftRoam orders: status, ETA window, gift, destination and the order token for tracking. Requires the authenticated GiftRoam connection (OAuth, scope orders:read); on a guest connection it returns auth_required. Never returns addresses, phone numbers or payment details.
This record as markdown: /tools/com-giftroam-giftroam/list-my-orders.md
What list_my_orders does on Giftroam
AI agents call list_my_orders 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 |
|---|---|---|---|
limit | integer | — | |
locale | string | — | Language of the conversation with the user (e.g. he-IL, fr-FR). Localizes content and messages; prices and availability are unaffected. |
Parameters from the server's own tool schema.
Why list_my_orders is rated Low
Even though list_my_orders 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 list_my_orders 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 list_my_orders, this is the rule to start with:
list_my_orders 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 list_my_orders call is checked against it from then on.
Questions about list_my_orders
The signed-in user's GiftRoam orders: status, ETA window, gift, destination and the order token for tracking. Requires the authenticated GiftRoam connection (OAuth, scope orders:read); on a guest connection it returns auth_required. Never returns addresses, phone numbers or payment details. It is categorised as a Read tool in the Giftroam MCP Server, which means it retrieves data without modifying state.
list_my_orders accepts 2 parameters: limit, locale. 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 list_my_orders: 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.
list_my_orders 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 list_my_orders 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 list_my_orders. 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.
list_my_orders 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