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.
This record as markdown: /tools/dev-cz-agents-dd/poll-isir-events.md
What poll_isir_events does on Isir
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.
| Parameter | Type | Required | Description |
|---|---|---|---|
since_id | integer | — | Last seen event id. Use 0 to start from the beginning of recorded ISIR history (~2008). |
Parameters from the server's own tool schema.
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 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.
Attacks that exploit this kind of access
The rule that runs poll_isir_events 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 poll_isir_events, this is the rule to start with:
poll_isir_events 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 poll_isir_events call is checked against it from then on.
Questions about 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. It is categorised as a Read tool in the Isir MCP Server, which means it retrieves data without modifying state.
poll_isir_events accepts 1 parameter: since_id. 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 poll_isir_events: 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.
poll_isir_events 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 poll_isir_events 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 poll_isir_events. 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.
poll_isir_events is provided by the Isir MCP server (https://isir.cz-agents.dev/mcp). 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