get_norwegian_company_legal_events
Legal events of a Norwegian company from the official Enhetsregisteret (Brønnøysundregistrene, NLOD 2.0): bankruptcy (konkurs, with the date the register publishes), voluntary winding-up, compulsory winding-up / forced dissolution, and strike-off — plus the current flags, re-checked live at call ...
This record as markdown: /tools/eu-sirenic-sirenic/get-norwegian-company-legal-events.md
What get_norwegian_company_legal_events does on Sirenic
AI agents call get_norwegian_company_legal_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 |
|---|---|---|---|
id | string | Yes | 9-digit Norwegian organisasjonsnummer, no spaces, e.g. 923609016 |
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_norwegian_company_legal_events is rated Low
Even though get_norwegian_company_legal_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_norwegian_company_legal_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_norwegian_company_legal_events, this is the rule to start with:
get_norwegian_company_legal_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_norwegian_company_legal_events call is checked against it from then on.
Questions about get_norwegian_company_legal_events
Legal events of a Norwegian company from the official Enhetsregisteret (Brønnøysundregistrene, NLOD 2.0): bankruptcy (konkurs, with the date the register publishes), voluntary winding-up, compulsory winding-up / forced dissolution, and strike-off — plus the current flags, re-checked live at call time. A registered company with no event returns an explicit positive answer (aucun_evenement: true), asserted only when the record was live-verified, no flag is raised, it is not struck off and the journal is current. Coarser than the French BODACC: the Norwegian bankruptcy register is not public, so there is no ruling text, no court and no insolvency practitioner; origine_date tells a register-published date from a Sirenic observation date, and date_au_plus_tard: true marks a date that is only an upper bound (flag already raised when first observed — started on or before). 3-year window (the source's own republication limit), except a still-open procedure, whose opening is always served. Only legal persons are served: natural-person forms (ENK, PERS, TVAM), estates named after one (KBO, BO) and any unrecognised form are refused. 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_norwegian_company_legal_events accepts 3 parameters: id, api_key, x_payment. Required: id. 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_norwegian_company_legal_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_norwegian_company_legal_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_norwegian_company_legal_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_norwegian_company_legal_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_norwegian_company_legal_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