# get_listing

Retrieve the full record for a single sanctions listing by its ID (format: ${source}:${source_list_id}, e.g. "ofac:12345" or "eu:EU.123.789").

Agent View of the PolicyLayer registry record for `get_listing`. HTML page: https://policylayer.com/tools/dev-cz-agents-isir/get-listing

## Facts

- Tool: `get_listing`
- Server: Isir (`@czagents/isir`) — https://policylayer.com/tools/dev-cz-agents-isir.md
- Install: `npx -y @czagents/isir`
- Homepage: https://github.com/martinhavel/cz-agents-mcp
- Risk category: Read (Low risk)
- Registry record: grade C, identity unverified
- Server auth posture: open
- Server rate-limited: yes
- Parameters: 1 (1 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `id` | string | yes | Internal listing ID, e.g. "ofac:12345". |

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_listing",
    "arguments": {
      "id": "<id>"
    }
  }
}
```

## Why get_listing is rated Low

This tool retrieves existing sanctions data by ID lookup. It performs a read-only query with no side effects, no data modification, and no destructive or financial actions. The operation is informational only. Severity is low because misuse would at worst expose publicly available sanctions information without causing harm.

From the tool's own definition: "Tool name 'get_listing' and description 'Retrieve the full record for a single sanctions listing by its ID' indicates a query/fetch operation with no modification capability."

## Use case

AI agents call get_listing to retrieve information from Isir 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 Isir:

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

## Other tools on Isir (5)

- `check_ico` — Read — https://policylayer.com/tools/dev-cz-agents-isir/check-ico.md
- `list_recent_updates` — Read — https://policylayer.com/tools/dev-cz-agents-isir/list-recent-updates.md
- `rescreen_portfolio` — Read — https://policylayer.com/tools/dev-cz-agents-isir/rescreen-portfolio.md
- `search_entity` — Read — https://policylayer.com/tools/dev-cz-agents-isir/search-entity.md
- `search_person` — Read — https://policylayer.com/tools/dev-cz-agents-isir/search-person.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=dev-cz-agents-isir · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/dev-cz-agents-isir