xero_create_invoice
AI agents use xero_create_invoice to create or update resources in WWIDE MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your WWIDE MCP Server environment.
Creating invoices is a Write operation that modifies financial records reversibly (invoices can be edited or voided). It is not Destructive (invoices aren't permanently deleted by creation) and not Financial (money doesn't move on invoice creation alone—payment collection is separate).
From the tool's definition Tool name 'xero_create_invoice' and server description stating 'CRUD operations' across Xero (accounting/financial platform). The prefix 'xero_create_' and suffix 'invoice' clearly indicate creation of financial documents.
Attacks that exploit this kind of access
xero_create_invoice. It is categorised as a Write tool in the WWIDE MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the WWIDE MCP Server MCP server in PolicyLayer and add a rule for xero_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 WWIDE MCP Server. Nothing to install.
xero_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 xero_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 xero_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.
xero_create_invoice is provided by the WWIDE MCP Server MCP server (kulvir88/salesforce-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 →