get_listing
Retrieve the full record for a single sanctions listing by its ID (format: ${source}:${source_list_id}, e.g. "ofac:12345" or "eu:EU.123.789").
This record as markdown: /tools/dev-cz-agents-isir/get-listing.md
What get_listing does on Isir
AI agents call get_listing 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 |
|---|---|---|---|
id | string | Yes | Internal listing ID, e.g. "ofac:12345". |
Parameters from the server's own tool schema.
Why get_listing is rated Low
This tool retrieves existing sanctions data by ID lookup. It performs a read-only query with no side effects, no data modification, and no destructive or financial actions. The operation is informational only. Severity is low because misuse would at worst expose publicly available sanctions information without causing harm.
From the tool's definition Tool name 'get_listing' and description 'Retrieve the full record for a single sanctions listing by its ID' indicates a query/fetch operation with no modification capability.
Attacks that exploit this kind of access
The rule that runs get_listing 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 get_listing, this is the rule to start with:
get_listing 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 get_listing call is checked against it from then on.
Questions about get_listing
Retrieve the full record for a single sanctions listing by its ID (format: ${source}:${source_list_id}, e.g. "ofac:12345" or "eu:EU.123.789"). It is categorised as a Read tool in the Isir MCP Server, which means it retrieves data without modifying state.
get_listing accepts 1 parameter: id. Required: id. 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 get_listing: 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.
get_listing 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 get_listing 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 get_listing. 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.
get_listing 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