get_estonian_company_registry_rulings
Registry rulings (määrused) of an Estonian company from the official e-Business Register open data (RIK, CC BY 4.0, DAILY national photo): registry entries, orders to remedy defects, warnings of striking-off for an unfiled annual report, warnings of compulsory dissolution for insufficient net ass...
This record as markdown: /tools/eu-sirenic-sirenic/get-estonian-company-registry-rulings.md
What get_estonian_company_registry_rulings does on Sirenic
AI agents call get_estonian_company_registry_rulings 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 |
|---|---|---|---|
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. |
registrikood | string | Yes | 8-digit Estonian registry code (registrikood, e-Business Register), e.g. 10003666 |
Parameters from the server's own tool schema.
Why get_estonian_company_registry_rulings is rated Low
Even though get_estonian_company_registry_rulings 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) · Bulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs get_estonian_company_registry_rulings 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_estonian_company_registry_rulings, this is the rule to start with:
get_estonian_company_registry_rulings 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_estonian_company_registry_rulings call is checked against it from then on.
Questions about get_estonian_company_registry_rulings
Registry rulings (määrused) of an Estonian company from the official e-Business Register open data (RIK, CC BY 4.0, DAILY national photo): registry entries, orders to remedy defects, warnings of striking-off for an unfiled annual report, warnings of compulsory dissolution for insufficient net assets, and annual-report fines, each with its date, extra deadline, status and force date, Estonian codes and labels as published. An alerte flag marks the CLOSED list of warning/fine types returned with the answer; nombre_alertes excludes only rulings whose etat_code is EXPLICITLY known as resolved (currently L only): a qualified ruling later resolved that way keeps alerte: true but no longer counts, while every other state (including J, K, or any code not yet seen) still counts, fail-closed on the unknown. types_non_qualifies lists this entity's other rule types, so a zero is never read as “no warning”. A still-registered entity with no ruling returns an explicit positive answer, dated with the photo actually served (photo_le); a struck-off entity leaves the open data entirely and returns 404 instead of a false clean sheet; so does a sole proprietorship (FIE) or an unrecognised legal form, not billed. 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_estonian_company_registry_rulings accepts 3 parameters: api_key, x_payment, registrikood. Required: registrikood. 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_estonian_company_registry_rulings: 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_estonian_company_registry_rulings 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_estonian_company_registry_rulings 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_estonian_company_registry_rulings. 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_estonian_company_registry_rulings 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