search_person
Fuzzy-search a sanctioned person by name across all loaded lists. Optional date of birth and nationality narrow results. Returns matches with confidence scores (0-100). 100 = exact ID match, 80+ = strong fuzzy match, lower = review needed.
This record as markdown: /tools/dev-cz-agents-isir/search-person.md
What search_person does on Isir
AI agents call search_person 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 |
|---|---|---|---|
dob | string | — | YYYY or YYYY-MM-DD. Optional, narrows matches. |
name | string | Yes | Full name. Cyrillic / Arabic / Chinese tolerated; transliteration applied. |
limit | integer | — | Max results (default 20). |
threshold | integer | — | Min confidence to include in results (default 80). |
nationality | string | — | Country name or ISO code. Optional. |
Parameters from the server's own tool schema.
Why search_person is rated Low
This tool retrieves and queries data from sanctioned person lists without creating, modifying, deleting, or executing any operations. It is a straightforward information lookup utility. Severity is low because read-only access to public/regulatory sanctioned-person lists poses minimal direct risk; misuse yields information exposure rather than operational or financial harm.
From the tool's definition Tool description explicitly states it performs 'Fuzzy-search' and 'Returns matches with confidence scores' — a query operation with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs search_person 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_person, this is the rule to start with:
search_person 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_person call is checked against it from then on.
Questions about search_person
Fuzzy-search a sanctioned person by name across all loaded lists. Optional date of birth and nationality narrow results. Returns matches with confidence scores (0-100). 100 = exact ID match, 80+ = strong fuzzy match, lower = review needed. It is categorised as a Read tool in the Isir MCP Server, which means it retrieves data without modifying state.
search_person accepts 5 parameters: dob, name, limit, threshold, nationality. 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_person: 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_person 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_person 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_person. 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_person 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