get_company_licences
Regulatory authorisations of a French company by SIREN: payment institution, e-money institution, account-information provider, payment agent or exempt entity (EBA PSD2 register, refreshed daily), insurance undertaking (EIOPA), electronic-communications operator (ARCEP) — with authorisation dates...
This record as markdown: /tools/eu-sirenic-sirenic/get-company-licences.md
What get_company_licences does on Sirenic
AI agents call get_company_licences 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 |
|---|---|---|---|
siren | string | Yes | 9-digit SIREN |
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_company_licences is rated Low
Even though get_company_licences 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_company_licences 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_company_licences, this is the rule to start with:
get_company_licences 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_company_licences call is checked against it from then on.
Questions about get_company_licences
Regulatory authorisations of a French company by SIREN: payment institution, e-money institution, account-information provider, payment agent or exempt entity (EBA PSD2 register, refreshed daily), insurance undertaking (EIOPA), electronic-communications operator (ARCEP) — with authorisation dates, licensed PSD2 services, EEA passporting and withdrawals. Use it before paying, onboarding or contracting with a regulated counterparty. Not authorised is an answer too. 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_company_licences accepts 3 parameters: siren, api_key, x_payment. Required: siren. 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_company_licences: 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_company_licences 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_company_licences 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_company_licences. 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_company_licences 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