AI agents use einvoice_generate_xrechnung to create or update resources in Einvoice — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Einvoice environment.
This tool creates/generates electronic invoice documents (XRechnung format), which are financial records. Generation of invoices creates new data artifacts that have legal and financial implications in the German e-invoicing system. This is a Write operation rather than Execute because it generates structured documents rather than executing arbitrary code.
From the tool's definition Tool name 'einvoice_generate_xrechnung' indicates generation of XRechnung 3.0 compliant invoices. Server description states the tool enables 'generate' operations for electronic invoices.
Attacks that exploit this kind of access
einvoice_generate_xrechnung. It is categorised as a Write tool in the Einvoice MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Einvoice MCP server in PolicyLayer and add a rule for einvoice_generate_xrechnung: 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 Einvoice. Nothing to install.
einvoice_generate_xrechnung is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the einvoice_generate_xrechnung 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 einvoice_generate_xrechnung. 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.
einvoice_generate_xrechnung is provided by the Einvoice MCP server (mavengence/einvoice-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →