# search_entity

Fuzzy-search a sanctioned entity (company, organization) by name. Optional country narrows results.

Agent View of the PolicyLayer registry record for `search_entity`. HTML page: https://policylayer.com/tools/dev-cz-agents-isir/search-entity

## Facts

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

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `name` | string | yes | Company / organization name. |
| `limit` | integer | no | Max results (default 20). |
| `country` | string | no | Country filter (name or ISO code). |
| `threshold` | integer | no | Min confidence (default 80). |

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_entity",
    "arguments": {
      "name": "<name>"
    }
  }
}
```

## Why search_entity is rated Low

This tool retrieves data from a sanctions registry without side effects. It queries existing records and returns results. No data is created, modified, deleted, or executed. This is a straightforward read-only operation typical of compliance/screening databases.

From the tool's own definition: "Tool performs 'Fuzzy-search' for sanctioned entities by name with optional country filter. No modification, deletion, or execution of code/commands. The description explicitly indicates a search/retrieval operation ('search', 'narrows results')."

## Use case

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

## Other tools on Isir (5)

- `check_ico` — Read — https://policylayer.com/tools/dev-cz-agents-isir/check-ico.md
- `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_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