create_einvoice · PDF Generator API MCP Server MCP

WHAT IT DOES

What create_einvoice does on PDF Generator API MCP Server

AI agents use create_einvoice to create or update resources in PDF Generator API MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your PDF Generator API MCP Server environment.

WHY IT NEEDS A POLICY

Why create_einvoice needs a policy

This tool creates financial documents (e-invoices) that have binding legal and accounting significance in B2B and B2G contexts. While it doesn't directly move money (Financial category), it generates official invoices that represent financial obligations and are used for billing purposes.

From the tool's definition Tool creates and generates e-invoices from JSON payloads, producing XML-based financial documents compliant with European EN 16931 standards.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_einvoice Rate-limited

create_einvoice stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_einvoice": {
      "limits": [
        {
          "counter": "create_einvoice_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches PDF Generator API MCP Server, so you can run agents against it safely.

FAQ

Questions about create_einvoice

What does the create_einvoice tool do? +

This endpoint transforms a JSON payload into an XML-based e-invoice that is fully compliant with the European EN 16931 standard. The generated output can be formatted in either UBL (Universal Business Language) or CII (Cross-Industry Invoice) syntax, ensuring interoperability across B2B and B2G platforms. The JSON payload follows Peppol BIS Billing 3.0 UBL Invoice described here: https://docs.peppol.eu/poacc/billing/3.0/. It is categorised as a Write tool in the PDF Generator API MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_einvoice? +

Register the PDF Generator API MCP Server MCP server in PolicyLayer and add a rule for create_einvoice: 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 PDF Generator API MCP Server. Nothing to install.

What risk level is create_einvoice? +

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

Can I rate-limit create_einvoice? +

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

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

create_einvoice is provided by the PDF Generator API MCP Server MCP server (pdfgeneratorapi/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.