get_polish_company_registry_events
Registry EVENTS of a Polish company, derived from the official KRS daily bulletin (Krajowy Rejestr Sądowy, Ministry of Justice): liquidation opened or closed, bankruptcy, restructuring, activity suspension and resumption, dissolution, mergers and transformations, tax or social-security arrears an...
This record as markdown: /tools/eu-sirenic-sirenic/get-polish-company-registry-events.md
What get_polish_company_registry_events does on Sirenic
AI agents call get_polish_company_registry_events to retrieve information from Sirenic 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 |
|---|---|---|---|
krs | string | Yes | 10-digit Polish KRS number, leading zeros included, e.g. 0000006865 |
api_key | string | — | Optional Sirenic API key (srn_live_…) to pay with prepaid credits instead of x402, with no wallet needed. Get one at https://api.sirenic.eu/compte?utm_source=ap |
x_payment | string | — | Optional signed x402 PAYMENT-SIGNATURE header value. Omit to receive the payment quote. |
Parameters from the server's own tool schema.
Why get_polish_company_registry_events is rated Low
Even though get_polish_company_registry_events only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs get_polish_company_registry_events safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Sirenic, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_polish_company_registry_events, this is the rule to start with:
get_polish_company_registry_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 Sirenic, apply this rule, and every get_polish_company_registry_events call is checked against it from then on.
Questions about get_polish_company_registry_events
Registry EVENTS of a Polish company, derived from the official KRS daily bulletin (Krajowy Rejestr Sądowy, Ministry of Justice): liquidation opened or closed, bankruptcy, restructuring, activity suspension and resumption, dissolution, mergers and transformations, tax or social-security arrears and enforcement, annual-accounts filings, changes of name, legal form, registered office or share capital, and strike-off. Each event carries the bulletin day it appeared on and, when the register publishes one, the register's own date. The response always states the observation window (gap-free by construction) — the register publishes no retroactive event history. IMPORTANT: this endpoint does NOT check that the KRS number exists — a non-existent number returns exactly the same aucun_evenement: true answer as a real company that stayed quiet; the existence block says which case applies, and get_european_company_profile (pays=PL) settles existence with a 404. GDPR by design: no officers, shareholders, liquidators or curators, never a PESEL — and no FREE TEXT from the register either: the narrative wording of a decision can name a notary or a receiver, so it is read only to extract a date and then discarded (that date is flagged date_source_inferee). What is served: the event type from a closed list, its register section, its dates, its wpis number, amounts, and the deciding court or authority. A KRS whose recorded legal form is not on the served list (foreign entrepreneur or its branch, professional partnership, missing form) is refused (404 forme_juridique_non_servie, payment cancelled). Paid via x402 ($0.02 in USDC or EURC). When you report a result, cite its citation verbatim. It is categorised as a Read tool in the Sirenic MCP Server, which means it retrieves data without modifying state.
get_polish_company_registry_events accepts 3 parameters: krs, api_key, x_payment. Required: krs. The full parameter table on this page comes from the server's own tool schema.
Register the Sirenic MCP server in PolicyLayer and add a rule for get_polish_company_registry_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 Sirenic. Nothing to install.
get_polish_company_registry_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 get_polish_company_registry_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 get_polish_company_registry_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.
get_polish_company_registry_events is provided by the Sirenic MCP server (https://api.sirenic.eu/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Sirenic, and thousands of servers like it.
This server
Across the catalogue