# rescreen_portfolio

PAID. Re-screen your own list of subjects against sanctions-list changes since a given date. Answers "which of MY clients were affected", which list_recent_updates cannot: that tool returns the global change feed, this one intersects it with your portfolio. Requires payment via x402; call without payment first to receive the terms.

Agent View of the PolicyLayer registry record for `rescreen_portfolio`. HTML page: https://policylayer.com/tools/dev-cz-agents-isir/rescreen-portfolio

## Facts

- Tool: `rescreen_portfolio`
- 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: 3 (2 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `since` | string | yes | ISO date of the last screening, e.g. "2026-07-01". |
| `source` | string | no |  |
| `subjects` | array | yes | Up to 11 subjects per paid call (batch cap sized to the per-call price, not per-subject). Each needs at least a name or an ICO. |

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": "rescreen_portfolio",
    "arguments": {
      "since": "<since>",
      "subjects": []
    }
  }
}
```

## Why rescreen_portfolio is rated Low

The primary function is to retrieve and cross-reference data (screening a portfolio against sanctions changes), which is fundamentally a Read operation—querying and analyzing existing information. Although payment is required, the tool itself does not execute financial transactions; it merely gates access.

From the tool's own definition: "Tool description states it 're-screen[s] your own list of subjects against sanctions-list changes' and 'intersects' a change feed with a portfolio to answer 'which of MY clients were affected'."

## Use case

AI agents call rescreen_portfolio 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": {
    "rescreen_portfolio": {}
  }
}
```

## 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
- `list_recent_updates` — Read — https://policylayer.com/tools/dev-cz-agents-isir/list-recent-updates.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