# search_packages

Search for eSIM data packages by country. Returns up to 10 packages per page sorted by price. Use the page parameter to paginate. No auth required. Call get_business_context first to understand IP routing and package types. Package types: - "regular": Fixed data pool (e.g. 3GB for 30 days). Best for most travelers. - "daily": Data resets each day (e.g. 2GB/day for 5 days). Good for short trips with predictable daily usage. Top-up days are available. IP routing (important for Asia): - "breakout": Local IP in destination country. Best for streaming, banking, social media. ALWAYS recommend by default. - "hk": Hong Kong IP. Cheapest but TikTok app and Facebook app are BLOCKED. - "nonhk": Third-country IP (UK, Singapore). No HK restrictions but IP won't match destination.

Agent View of the PolicyLayer registry record for `search_packages`. HTML page: https://policylayer.com/tools/com-gitsim-chat/search-packages

## Facts

- Tool: `search_packages`
- Server: Gitsim Chat (`https://chat.gitsim.com/api/mcp`) — https://policylayer.com/tools/com-gitsim-chat.md
- Homepage: https://github.com/https://chat.gitsim.com/api/mcp
- Risk category: Read (Low risk)
- Registry record: grade C, identity unverified
- Server auth posture: open
- Server rate-limited: no
- Parameters: 10 (1 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `name` | string | no | Case-insensitive substring match on package name |
| `page` | integer | no | Page number (1-based, default 1). Each page returns up to 10 results. |
| `type` | string | no | "daily" = data resets each day (e.g. 2GB/day for 5 days, can top-up days). "regular" = fixed data pool for the full duration. Omit for both. |
| `country` | string | yes | ISO 3166-1 alpha-2 country code, e.g. JP, TH, US |
| `ip_route` | string | no | Filter by IP routing type. "breakout" = local IP (recommended default), "hk" = Hong Kong IP (restricted, cheapest), "nonhk" = other breakout (no HK restrictions |
| `is_regional` | boolean | no | true = only multi-country/regional packages (e.g. Europe, Asia). false = only single-country packages. Omit for both. |
| `max_data_gb` | number | no | Maximum data in GB. For daily packages this is the per-day amount. |
| `min_data_gb` | number | no | Minimum data in GB. For daily packages this is the per-day amount. |
| `max_duration_days` | number | no | Maximum duration in days |
| `min_duration_days` | number | no | Minimum duration in days |

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

## Why search_packages is rated Low

search_packages performs a search query that returns filtered and paginated results. It has no side effects, does not create, modify, delete, or execute external operations. The function is purely informational, displaying available eSIM packages to facilitate user browsing before purchase. Even though this is part of an eSIM management platform, the tool itself only reads and returns data.

From the tool's own definition: "Tool description states: 'Search for eSIM data packages by country. Returns up to 10 packages per page sorted by price. Use the page parameter to paginate."

Risk signals: High parameter count (10 properties)

## Use case

AI agents call search_packages 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.

## Recommended policy (PolicyLayer)

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

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

## Other tools on Gitsim Chat (8)

- `buy_topup` — Financial — https://policylayer.com/tools/com-gitsim-chat/buy-topup.md
- `create_order` — Financial — https://policylayer.com/tools/com-gitsim-chat/create-order.md
- `check_data_balance` — Read — https://policylayer.com/tools/com-gitsim-chat/check-data-balance.md
- `check_order_status` — Read — https://policylayer.com/tools/com-gitsim-chat/check-order-status.md
- `get_business_context` — Read — https://policylayer.com/tools/com-gitsim-chat/get-business-context.md
- `get_package` — Read — https://policylayer.com/tools/com-gitsim-chat/get-package.md
- `list_esims` — Read — https://policylayer.com/tools/com-gitsim-chat/list-esims.md
- `search_topup_packages` — Read — https://policylayer.com/tools/com-gitsim-chat/search-topup-packages.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-gitsim-chat · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-gitsim-chat