validate_invoice

Validate a UBL 2.1 invoice (or credit note) XML string against the official EN 16931 Schematron. Returns whether it is valid and any failing BR-* business rules.

SERVERInvoicehub SOURCEhttps://api.invoicehub.dev/mcp

Low RISK CLASS

Category Read

Parameters 11 required

Recommended Allowedsee the rule below

Registry record Grade C, identity unverified Pull the record →

This record as markdown: /tools/dev-invoicehub-invoicehub/validate-invoice.md

WHAT IT DOES

What validate_invoice does on Invoicehub

AI agents call validate_invoice to retrieve information from Invoicehub 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
`xml`	string	Yes	Raw UBL 2.1 invoice XML.

Parameters from the server's own tool schema.

RISK

Why validate_invoice is rated Low

Even though validate_invoice 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

RECOMMENDED RULE

The rule that runs validate_invoice safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Invoicehub, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For validate_invoice, this is the rule to start with:

validate_invoice Allowed

validate_invoice is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "validate_invoice": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Invoicehub, apply this rule, and every validate_invoice call is checked against it from then on.

FAQ

Questions about validate_invoice

What does the validate_invoice tool do? +

Validate a UBL 2.1 invoice (or credit note) XML string against the official EN 16931 Schematron. Returns whether it is valid and any failing BR-* business rules. It is categorised as a Read tool in the Invoicehub MCP Server, which means it retrieves data without modifying state.

What parameters does validate_invoice accept? +

validate_invoice accepts 1 parameter: xml. Required: xml. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on validate_invoice? +

Register the Invoicehub MCP server in PolicyLayer and add a rule for validate_invoice: 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 Invoicehub. Nothing to install.

What risk level is validate_invoice? +

validate_invoice is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit validate_invoice? +

Yes. Add a rate_limit block to the validate_invoice 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 validate_invoice completely? +

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

validate_invoice is provided by the Invoicehub MCP server (https://api.invoicehub.dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Invoicehub, and thousands of servers like it.

This server

All 4 Invoicehub tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →