list_recent_updates
List sanctions added/removed/modified since a given date. Use for daily monitoring against a watchlist.
This record as markdown: /tools/dev-cz-agents-isir/list-recent-updates.md
What list_recent_updates does on Isir
AI agents call list_recent_updates 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 |
|---|---|---|---|
since | string | Yes | ISO date or datetime, e.g. "2026-04-01" or "2026-04-01T00:00:00Z". |
source | string | — | Optional source filter. |
Parameters from the server's own tool schema.
Why list_recent_updates is rated Low
This tool retrieves and lists changes to sanctions data within a date range. It performs a query operation with no side effects, no data modification, no code execution, and no financial impact. The explicit mention of 'monitoring' indicates its role is informational/observational only.
From the tool's definition Tool description states 'List sanctions added/removed/modified since a given date' — a retrieval operation with 'Use for daily monitoring' indicating passive querying against existing data. No create, modify, delete, execute, or financial operations.
Attacks that exploit this kind of access
The rule that runs list_recent_updates 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 list_recent_updates, this is the rule to start with:
list_recent_updates 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 list_recent_updates call is checked against it from then on.
Questions about list_recent_updates
List sanctions added/removed/modified since a given date. Use for daily monitoring against a watchlist. It is categorised as a Read tool in the Isir MCP Server, which means it retrieves data without modifying state.
list_recent_updates accepts 2 parameters: since, source. Required: since. 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 list_recent_updates: 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.
list_recent_updates 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 list_recent_updates 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 list_recent_updates. 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.
list_recent_updates 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