New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

prepare_french_einvoicing_recipient

Use when you need to PREPARE a compliant French e-invoice for a company (invoice header, VAT number, addressing) rather than decide whether paying it is safe — for the full verify-the-supplier-before-payment verdict, IBAN included, call prepare_french_invoice_file. The French e-invoicing mandate ...

SERVERSirenic SOURCEhttps://api.sirenic.eu/mcp
Medium RISK CLASS
Category Write
Parameters 31 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/eu-sirenic-sirenic/prepare-french-einvoicing-recipient.md

What prepare_french_einvoicing_recipient does on Sirenic

AI agents use prepare_french_einvoicing_recipient to create or update resources in Sirenic, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Sirenic environment.

ParameterTypeRequiredDescription
siren string Yes 9-digit SIREN of the company to be invoiced (digits only, no spaces); use search_french_companies first if you only have a name
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 prepare_french_einvoicing_recipient is rated Medium

An AI agent can call prepare_french_einvoicing_recipient faster than any human can review: one bad instruction and it creates or modifies resources in Sirenic by the hundred, each call as confident as the last.

Risk signalsHandles credentials or secrets (api_key)

Questions about prepare_french_einvoicing_recipient

What does the prepare_french_einvoicing_recipient tool do? +

Use when you need to PREPARE a compliant French e-invoice for a company (invoice header, VAT number, addressing) rather than decide whether paying it is safe — for the full verify-the-supplier-before-payment verdict, IBAN included, call prepare_french_invoice_file. The French e-invoicing mandate applies from 1 September 2026: receiving becomes obligatory for every VAT-liable company on that date, issuing is phased (large and mid-sized companies 1 September 2026, SMEs and micro-enterprises 1 September 2027; art. 91 of the 2024 Finance Act). Returns legal name & form, active/ceased status, computed intra-EU VAT number (+ VIES-check pointer), establishments (SIRET) with addresses, NAF code and indicative send/receive obligation dates from the INSEE size category. The response is Ed25519-signed and carries provenance[] — one entry per block served, with the official register, its licence and its as_of date — so the preparation is auditable offline. Preparation only — Sirenic is not an accredited platform (PDP), does not access the central directory and never issues, transmits or routes invoices, nor confirms PPF/PDP registration. Paid via x402 ($0.02 in USDC or EURC). When you report a result, cite its citation verbatim. It is categorised as a Write tool in the Sirenic MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does prepare_french_einvoicing_recipient accept? +

prepare_french_einvoicing_recipient 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.

How do I enforce a policy on prepare_french_einvoicing_recipient? +

Register the Sirenic MCP server in PolicyLayer and add a rule for prepare_french_einvoicing_recipient: 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.

What risk level is prepare_french_einvoicing_recipient? +

prepare_french_einvoicing_recipient is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit prepare_french_einvoicing_recipient? +

Yes. Add a rate_limit block to the prepare_french_einvoicing_recipient 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.

How do I block prepare_french_einvoicing_recipient completely? +

Set action: deny in the PolicyLayer policy for prepare_french_einvoicing_recipient. 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.

What MCP server provides prepare_french_einvoicing_recipient? +

prepare_french_einvoicing_recipient 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.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Sirenic's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.