AI agents call xero_bank_transactions to retrieve information from UnClick without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
date_to | string | — | |
date_from | string | — | |
tenant_id | string | — | |
access_token | string | — | |
bank_account_id | string | — |
Parameters from the server's own tool schema.
This tool retrieves existing financial data from a Xero accounting system. While it accesses sensitive financial information (bank transactions), the operation is read-only with no capability to modify, delete, or execute actions. The severity is low because access is limited to data retrieval; blast radius of misuse is confined to information disclosure rather than financial transactions or destructive changes.
From the tool's definition Tool name 'xero_bank_transactions' and description 'Get bank transactions from Xero' indicate a retrieval operation with the verb 'Get', which performs no modifications or side effects.
Risk signalsHandles credentials or secrets (access_token)
Attacks that exploit this kind of access
Get bank transactions from Xero. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
xero_bank_transactions accepts 5 parameters: date_to, date_from, tenant_id, access_token, bank_account_id. 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_bank_transactions: 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_bank_transactions 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_bank_transactions 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_bank_transactions. 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_bank_transactions is provided by the UnClick MCP server (@unclick/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 →