Add invoice to an order
AI agents use vtex_invoice_order to create or update resources in MCP VTEX Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP VTEX Server environment.
This tool creates or adds invoice records to orders, which is a Write action (creates/modifies data reversibly). While invoices have financial implications, the tool itself doesn't move money or create financial obligations—it documents/records an existing transaction. However, invoices are legally binding documents tied to payment and tax obligations, making this a high-severity Write action.
From the tool's definition Tool name is 'vtex_invoice_order' and description states 'Add invoice to an order'. The action of adding/creating an invoice modifies order records and financial documentation, which are critical business data.
Attacks that exploit this kind of access
Add invoice to an order. It is categorised as a Write tool in the MCP VTEX Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP VTEX Server MCP server in PolicyLayer and add a rule for vtex_invoice_order: 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 MCP VTEX Server. Nothing to install.
vtex_invoice_order 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 vtex_invoice_order 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 vtex_invoice_order. 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.
vtex_invoice_order is provided by the MCP VTEX Server MCP server (leosepulveda/mcp-vtex). 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 →