CREATE INVOICE - Create an invoice for an order.
AI agents use tiendanube_create_invoice to create or update resources in Tienda Nube MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Tienda Nube MCP Server environment.
Creating an invoice is a reversible write operation that modifies order-related data and generates new financial documentation. While invoices have business significance, the tool creates/generates documents rather than moving money or triggering payments (which would be Financial category).
From the tool's definition Tool name contains 'create' and description explicitly states 'Create an invoice for an order', indicating data creation operation.
Attacks that exploit this kind of access
CREATE INVOICE - Create an invoice for an order. It is categorised as a Write tool in the Tienda Nube MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Tienda Nube MCP Server MCP server in PolicyLayer and add a rule for tiendanube_create_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 Tienda Nube MCP Server. Nothing to install.
tiendanube_create_invoice 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 tiendanube_create_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.
Set action: deny in the PolicyLayer policy for tiendanube_create_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.
tiendanube_create_invoice is provided by the Tienda Nube MCP Server MCP server (pedrohsguimaraes/nuvem-shop-mcp-server). 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 →