# list_recent_updates

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

Agent View of the PolicyLayer registry record for `list_recent_updates`. HTML page: https://policylayer.com/tools/dev-cz-agents-isir/list-recent-updates

## Facts

- Tool: `list_recent_updates`
- Server: Isir (`@czagents/isir`) — https://policylayer.com/tools/dev-cz-agents-isir.md
- Install: `npx -y @czagents/isir`
- Homepage: https://github.com/martinhavel/cz-agents-mcp
- Risk category: Read (Low risk)
- Registry record: grade C, identity unverified
- Server auth posture: open
- Server rate-limited: yes
- Parameters: 2 (1 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `since` | string | yes | ISO date or datetime, e.g. "2026-04-01" or "2026-04-01T00:00:00Z". |
| `source` | string | no | Optional source filter. |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "list_recent_updates",
    "arguments": {
      "since": "<since>"
    }
  }
}
```

## 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 own 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."

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Isir:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_recent_updates": {}
  }
}
```

## Other tools on Isir (5)

- `check_ico` — Read — https://policylayer.com/tools/dev-cz-agents-isir/check-ico.md
- `get_listing` — Read — https://policylayer.com/tools/dev-cz-agents-isir/get-listing.md
- `rescreen_portfolio` — Read — https://policylayer.com/tools/dev-cz-agents-isir/rescreen-portfolio.md
- `search_entity` — Read — https://policylayer.com/tools/dev-cz-agents-isir/search-entity.md
- `search_person` — Read — https://policylayer.com/tools/dev-cz-agents-isir/search-person.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=dev-cz-agents-isir · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/dev-cz-agents-isir