# check_ico

Check whether a Czech IČO (or any company by IČO) appears on sanctions lists. Direct exact-ID lookup; pass name to also fuzzy-match if no direct hit.

Agent View of the PolicyLayer registry record for `check_ico`. HTML page: https://policylayer.com/tools/dev-cz-agents-isir/check-ico

## Facts

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

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `ico` | string | yes | Czech IČO (7-8 digits) or comparable national company ID. |
| `name` | string | no | Optional company name for fuzzy fallback if IČO not directly listed. |

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_ico",
    "arguments": {
      "ico": "<ico>"
    }
  }
}
```

## Why check_ico is rated Low

This tool retrieves compliance/sanctions status information for a given IČO identifier. It queries a reference database but does not create, modify, delete, or execute any external operations. The fuzzy-match option via name parameter remains a read operation. Severity is low because misuse (e.g., checking unrelated entities) causes no operational harm—it only returns informational data.

From the tool's own definition: "Tool performs 'check' and 'lookup' operations against sanctions lists, returning status data without modifying records. Description emphasizes querying ('appears on sanctions lists', 'lookup') with no side effects mentioned."

## Use case

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

## Other tools on Isir (5)

- `get_listing` — Read — https://policylayer.com/tools/dev-cz-agents-isir/get-listing.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