validate_eu_vat_number
VAT number check against VIES: use when you only need the tax half of verifying a supplier before payment: confirm that a counterparty's intra-community VAT number really exists before invoicing it, applying the reverse charge or paying it. It is a required check under the French e-invoicing mand...
This record as markdown: /tools/eu-sirenic-sirenic/validate-eu-vat-number.md
What validate_eu_vat_number does on Sirenic
AI agents call validate_eu_vat_number 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. |
vat_number | string | Yes | Full VAT number with its 2-letter country prefix and no spaces, e.g. FR27552032534 |
Parameters from the server's own tool schema.
Why validate_eu_vat_number is rated Low
Even though validate_eu_vat_number 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 validate_eu_vat_number 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 validate_eu_vat_number, this is the rule to start with:
validate_eu_vat_number 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 validate_eu_vat_number call is checked against it from then on.
Questions about validate_eu_vat_number
VAT number check against VIES: use when you only need the tax half of verifying a supplier before payment: confirm that a counterparty's intra-community VAT number really exists before invoicing it, applying the reverse charge or paying it. It is a required check under the French e-invoicing mandate of 1 September 2026 and under the Belgian B2B mandate in force since 1 January 2026. Validates any EU intra-community VAT number against the official VIES service (all member states) and returns valid / invalid / unavailable, the registered name and address when the member state publishes them, and the VIES consultation identifier as proof. Name and address are served only for a holder that its number's format or its country's register (BE, PL, LV, HR, RO, SE, CZ, DK, FI, FR) proves a legal person; any other holder (natural person, undecided form, missing from its register, or in a state where no register qualifies it: AT, CY, DE, EE, EL, HU, IE, IT, LT, LU, MT, NL, SI, SK, XI) gets neither, the omission counted in ecartes by reason. A member-state outage is reported as unavailable, never as a false invalid. The response is Ed25519-signed and carries provenance[]: the VIES entry with the date the number was really consulted, never a fabricated one. Paid via x402 ($0.003 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.
validate_eu_vat_number accepts 3 parameters: api_key, x_payment, vat_number. Required: vat_number. 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 validate_eu_vat_number: 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.
validate_eu_vat_number 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 validate_eu_vat_number 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 validate_eu_vat_number. 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.
validate_eu_vat_number 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