# get_package

Get details for a specific eSIM package by its ID. No authentication required.

Agent View of the PolicyLayer registry record for `get_package`. HTML page: https://policylayer.com/tools/com-gitsim-chat/get-package

## Facts

- Tool: `get_package`
- 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: 1 (1 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `package_id` | string | yes | The package ID to look up |

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": "get_package",
    "arguments": {
      "package_id": "<package_id>"
    }
  }
}
```

## Why get_package is rated Low

This tool retrieves package details without modifying, deleting, or executing operations. The 'No authentication required' further confirms it is a simple informational lookup. It poses minimal risk as it only exposes existing package data.

From the tool's own definition: "Tool name 'get_package' and description 'Get details for a specific eSIM package' indicates data retrieval. Verb 'Get' and context of querying package information by ID are characteristic of read operations with no side effects."

## Use case

AI agents call get_package 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": {
    "get_package": {}
  }
}
```

## 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
- `list_esims` — Read — https://policylayer.com/tools/com-gitsim-chat/list-esims.md
- `search_packages` — Read — https://policylayer.com/tools/com-gitsim-chat/search-packages.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