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.
This record as markdown: /tools/dev-cz-agents-isir/check-ico.md
What check_ico does on Isir
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.
| Parameter | Type | Required | Description |
|---|---|---|---|
ico | string | Yes | Czech IČO (7-8 digits) or comparable national company ID. |
name | string | — | Optional company name for fuzzy fallback if IČO not directly listed. |
Parameters from the server's own tool schema.
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 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.
Attacks that exploit this kind of access
The rule that runs check_ico 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 check_ico, this is the rule to start with:
check_ico 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 check_ico call is checked against it from then on.
Questions about 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. It is categorised as a Read tool in the Isir MCP Server, which means it retrieves data without modifying state.
check_ico accepts 2 parameters: ico, name. Required: ico. 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 check_ico: 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.
check_ico 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 check_ico 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 check_ico. 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.
check_ico 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