check_delivery
Is delivery to a country (optionally a city, by a date, for a specific gift) feasible? Returns earliest/latest estimate and warnings (PO box, hotel, holiday window) with a suggested action. Use it whenever the user has a deadline.
This record as markdown: /tools/com-giftroam-giftroam/check-delivery.md
What check_delivery does on Giftroam
AI agents call check_delivery 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 |
|---|---|---|---|
city | string | — | Destination city (used for warnings only; never store addresses in chat). |
locale | string | — | Language of the conversation with the user (e.g. he-IL, fr-FR). Localizes content and messages; prices and availability are unaffected. |
country | string | Yes | Destination country, ISO-3166 alpha-2. |
gift_id | string | — | Optional gift_id to use that gift's delivery window. |
date_needed | string | — | YYYY-MM-DD the gift must arrive by. |
Parameters from the server's own tool schema.
Why check_delivery is rated Low
Even though check_delivery 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 check_delivery 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 check_delivery, this is the rule to start with:
check_delivery 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 check_delivery call is checked against it from then on.
Questions about check_delivery
Is delivery to a country (optionally a city, by a date, for a specific gift) feasible? Returns earliest/latest estimate and warnings (PO box, hotel, holiday window) with a suggested action. Use it whenever the user has a deadline. It is categorised as a Read tool in the Giftroam MCP Server, which means it retrieves data without modifying state.
check_delivery accepts 5 parameters: city, locale, country, gift_id, date_needed. Required: country. 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 check_delivery: 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.
check_delivery 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_delivery 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_delivery. 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_delivery 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