get_swiss_company_events
Swiss company commercial-register publications from the Swiss Official Gazette of Commerce (SOGC/SHAB, SECO, public API, live with a 24 h cache, online since July 2018): every registration, change and deletion carrying the company's UID, newest first: date, publication number, canton, office, the...
This record as markdown: /tools/eu-sirenic-sirenic/get-swiss-company-events.md
What get_swiss_company_events does on Sirenic
AI agents call get_swiss_company_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 | Swiss UID (Unternehmens-Identifikationsnummer), CHE-xxx.xxx.xxx, e.g. CHE-102.732.681 |
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_swiss_company_events is rated Low
Even though get_swiss_company_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) · Bulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs get_swiss_company_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_swiss_company_events, this is the rule to start with:
get_swiss_company_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_swiss_company_events call is checked against it from then on.
Questions about get_swiss_company_events
Swiss company commercial-register publications from the Swiss Official Gazette of Commerce (SOGC/SHAB, SECO, public API, live with a 24 h cache, online since July 2018): every registration, change and deletion carrying the company's UID, newest first: date, publication number, canton, office, the company as published (name, UID, seat, eCH legal-form code, purpose, capital, address without the c/o line) before and after the change, and closed-list change flags (name, seat, address, purpose, capital, legal form, bankruptcy, liquidation, suspension, re-entry, other entries). The published free text is withheld (texte_retenu: true): it names persons. Beyond 60 listed publications they are detailed newest first until 60 servable ones are found (200 more details at most), and troncature says when some are not. A publication whose company is a sole proprietorship (before or after the change) is left out and counted in ecartes. Unknown UID, sole proprietorship (Einzelunternehmen), branch without a served head office or undecided legal form = 404 (no charge), as for the profile. 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_swiss_company_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_swiss_company_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_swiss_company_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_swiss_company_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_swiss_company_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_swiss_company_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