AI agents call einvoice_validate_xrechnung to retrieve information from Einvoice without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs validation—a read-only operation that checks an XRechnung invoice (CII XML format) against the KoSIT validator rules. Validation has no side effects on the invoice data itself; it merely reports compliance status. No data is created, modified, deleted, or financial operations are triggered. This is a typical Read category tool.
From the tool's definition Tool name 'validate' and description 'Validiert eine XRechnung (CII XML) gegen den KoSIT-Validator' indicate the tool checks/validates invoice format against a validation standard without modifying, generating, or deleting data.
Attacks that exploit this kind of access
Validiert eine XRechnung (CII XML) gegen den KoSIT-Validator. It is categorised as a Read tool in the Einvoice MCP Server, which means it retrieves data without modifying state.
Register the Einvoice MCP server in PolicyLayer and add a rule for einvoice_validate_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_validate_xrechnung 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 einvoice_validate_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_validate_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_validate_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 →