search_entity
Fuzzy-search a sanctioned entity (company, organization) by name. Optional country narrows results.
This record as markdown: /tools/dev-cz-agents-isir/search-entity.md
What search_entity does on Isir
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.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | Yes | Company / organization name. |
limit | integer | — | Max results (default 20). |
country | string | — | Country filter (name or ISO code). |
threshold | integer | — | Min confidence (default 80). |
Parameters from the server's own tool schema.
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 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').
Attacks that exploit this kind of access
The rule that runs search_entity safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Isir, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For search_entity, this is the rule to start with:
search_entity is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Isir, apply this rule, and every search_entity call is checked against it from then on.
Questions about search_entity
Fuzzy-search a sanctioned entity (company, organization) by name. Optional country narrows results. It is categorised as a Read tool in the Isir MCP Server, which means it retrieves data without modifying state.
search_entity accepts 4 parameters: name, limit, country, threshold. Required: name. The full parameter table on this page comes from the server's own tool schema.
Register the Isir MCP server in PolicyLayer and add a rule for search_entity: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Isir. Nothing to install.
search_entity is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the search_entity rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for search_entity. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
search_entity is provided by the Isir MCP server (@czagents/isir). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Isir, and thousands of servers like it.
This server
Across the catalogue