# poll_isir_events

Pull a batch of recent ISIR events (insolvency register publications) since the given event id. ISIR is an append-only feed — each call returns up to ~1000 events newer than since_id. Use last_id from response as next since_id. Useful for compliance monitoring or to back-fill an index.

Agent View of the PolicyLayer registry record for `poll_isir_events`. HTML page: https://policylayer.com/tools/dev-cz-agents-dd/poll-isir-events

## Facts

- Tool: `poll_isir_events`
- Server: Isir (`https://isir.cz-agents.dev/mcp`) — https://policylayer.com/tools/dev-cz-agents-dd.md
- 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: 1
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `since_id` | integer | no | Last seen event id. Use 0 to start from the beginning of recorded ISIR history (~2008). |

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": "poll_isir_events",
    "arguments": {}
  }
}
```

## Why poll_isir_events is rated Low

This tool retrieves and queries data from an append-only insolvency register feed with no side effects. It is designed for compliance monitoring and backfilling indexes—both read-only operations. There is no capability to modify, delete, or execute external actions.

From the tool's own definition: "Tool description states 'Pull a batch of recent ISIR events' and 'each call returns up to ~1000 events'. Keywords: 'pull', 'returns', 'append-only feed'. No mutation, creation, deletion, or execution of code implied."

## Use case

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

## Other tools on Isir (2)

- `check_ico_insolvency` — Read — https://policylayer.com/tools/dev-cz-agents-dd/check-ico-insolvency.md
- `search_person_insolvency` — Read — https://policylayer.com/tools/dev-cz-agents-dd/search-person-insolvency.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-dd · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/dev-cz-agents-dd