# 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.

Agent View of the PolicyLayer registry record for `check_delivery`. HTML page: https://policylayer.com/tools/com-giftroam-giftroam/check-delivery

## Facts

- Tool: `check_delivery`
- Server: Giftroam (`https://mcp.giftroam.com/mcp`) — https://policylayer.com/tools/com-giftroam-giftroam.md
- Homepage: https://github.com/https://mcp.giftroam.com/mcp
- Risk category: Read (Low risk)
- Registry record: grade C, identity unverified
- Server auth posture: open
- Server CORS policy: *
- Server rate-limited: no
- Parameters: 5 (1 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `city` | string | no | Destination city (used for warnings only; never store addresses in chat). |
| `locale` | string | no | 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 | no | Optional gift_id to use that gift's delivery window. |
| `date_needed` | string | no | YYYY-MM-DD the gift must arrive by. |

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_delivery",
    "arguments": {
      "country": "<country>"
    }
  }
}
```

## 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.

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Giftroam:

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

## Other tools on Giftroam (5)

- `get_gift_details` — Read — https://policylayer.com/tools/com-giftroam-giftroam/get-gift-details.md
- `get_order_status` — Read — https://policylayer.com/tools/com-giftroam-giftroam/get-order-status.md
- `list_my_orders` — Read — https://policylayer.com/tools/com-giftroam-giftroam/list-my-orders.md
- `search_gifts` — Read — https://policylayer.com/tools/com-giftroam-giftroam/search-gifts.md
- `create_checkout` — Write — https://policylayer.com/tools/com-giftroam-giftroam/create-checkout.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-giftroam-giftroam · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-giftroam-giftroam