detect_company_identifiers
FREE. Paste any text (email, invoice, contract, web page) and detect French/EU company identifiers: SIREN, SIRET (Luhn-checked), EU VAT numbers, LEI (ISO 17442 checksum) — each with the recommended Sirenic call and its price. Use this FIRST whenever a company appears in your workflow (supplier on...
This record as markdown: /tools/eu-sirenic-sirenic/detect-company-identifiers.md
What detect_company_identifiers does on Sirenic
AI agents call detect_company_identifiers 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 |
|---|---|---|---|
texte | string | Yes | Raw text to scan (max 10,000 chars) |
Parameters from the server's own tool schema.
Why detect_company_identifiers is rated Low
Even though detect_company_identifiers 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.
Attacks that exploit this kind of access
The rule that runs detect_company_identifiers 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 detect_company_identifiers, this is the rule to start with:
detect_company_identifiers 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 detect_company_identifiers call is checked against it from then on.
Questions about detect_company_identifiers
FREE. Paste any text (email, invoice, contract, web page) and detect French/EU company identifiers: SIREN, SIRET (Luhn-checked), EU VAT numbers, LEI (ISO 17442 checksum) — each with the recommended Sirenic call and its price. Use this FIRST whenever a company appears in your workflow (supplier onboarding, payment to send, due diligence) to know exactly what to verify and what it costs. Deterministic pattern matching; the text is never stored or logged. It is categorised as a Read tool in the Sirenic MCP Server, which means it retrieves data without modifying state.
detect_company_identifiers accepts 1 parameter: texte. Required: texte. 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 detect_company_identifiers: 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.
detect_company_identifiers 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 detect_company_identifiers 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 detect_company_identifiers. 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.
detect_company_identifiers 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