Get invoices from Xero.
AI agents call xero_get_invoices to retrieve information from WWIDE MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves invoice data from Xero without side effects. It performs a read-only query operation, consistent with the Read category pattern (get/fetch). The severity is low because retrieval of financial records poses minimal risk compared to modification or deletion—exposure of invoice data may have privacy implications but the tool itself cannot alter financial state or transactions.
From the tool's definition Tool name 'xero_get_invoices' and description 'Get invoices from Xero' indicate a retrieval operation with no modification or deletion of data.
Attacks that exploit this kind of access
Get invoices from Xero. It is categorised as a Read tool in the WWIDE MCP Server MCP Server, which means it retrieves data without modifying state.
Register the WWIDE MCP Server MCP server in PolicyLayer and add a rule for xero_get_invoices: 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_get_invoices is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the xero_get_invoices 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_get_invoices. 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_get_invoices 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 →