AI agents use facturx_create_pdf to create or update resources in Facturx — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Facturx environment.
This tool creates and generates PDF documents with embedded invoice data. While it produces output files, the action is reversible (PDFs can be deleted or regenerated) and has no destructive, financial, or code execution impact. It represents document creation/generation, which falls under Write category.
From the tool's definition Tool name 'facturx_create_pdf' and description 'Crée un PDF avec le XML Factur-X embarqué en pièce jointe' (Creates a PDF with embedded Factur-X XML as attachment) indicate generation of a new document artifact.
Attacks that exploit this kind of access
Crée un PDF avec le XML Factur-X embarqué en pièce jointe (format requis par la norme). It is categorised as a Write tool in the Facturx MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Facturx MCP server in PolicyLayer and add a rule for facturx_create_pdf: 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 Facturx. Nothing to install.
facturx_create_pdf 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 facturx_create_pdf 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 facturx_create_pdf. 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.
facturx_create_pdf is provided by the Facturx MCP server (samdreamsmaker/facturx-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 →