New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

list_recent_updates

List sanctions added/removed/modified since a given date. Use for daily monitoring against a watchlist.

SERVERIsir SOURCE@czagents/isir
Low RISK CLASS
Category Read
Parameters 21 required
Recommended Allowedsee the rule below
Registry record Grade C, identity unverified Pull the record →

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.

ParameterTypeRequiredDescription
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.

Questions about list_recent_updates

What does the list_recent_updates tool do? +

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.

What parameters does list_recent_updates accept? +

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.

How do I enforce a policy on list_recent_updates? +

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.

What risk level is list_recent_updates? +

list_recent_updates is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_recent_updates? +

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.

How do I block list_recent_updates completely? +

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.

What MCP server provides list_recent_updates? +

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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Isir's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.