This record as markdown: /tools/creativelead-unclick/xero-invoices.md
What xero_invoices does on UnClick
AI agents call xero_invoices to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
status | string | — | DRAFT, SUBMITTED, AUTHORISED, etc. |
date_to | string | — | |
date_from | string | — | |
tenant_id | string | — | |
contact_id | string | — | |
access_token | string | — |
Parameters from the server's own tool schema.
Why xero_invoices is rated Low
This tool retrieves invoice data from the Xero accounting system. It is a read-only operation that queries and returns existing financial records without creating, modifying, deleting, or executing any side effects. While the data is financial in nature, the action itself is passive data retrieval, which falls under the Read category.
From the tool's definition Tool name 'xero_invoices' and description 'Get invoices from Xero' indicate a retrieval operation with no modification or deletion of data.
Risk signalsHandles credentials or secrets (access_token)
Attacks that exploit this kind of access
The rule that runs xero_invoices safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For xero_invoices, this is the rule to start with:
xero_invoices is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every xero_invoices call is checked against it from then on.
Questions about xero_invoices
Get invoices from Xero. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
xero_invoices accepts 6 parameters: status, date_to, date_from, tenant_id, contact_id, access_token. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for xero_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 UnClick. Nothing to install.
xero_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_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_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_invoices is provided by the UnClick MCP server (creativelead/unclick). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue