This record as markdown: /tools/creativelead-unclick/xero-bank-transactions.md
What xero_bank_transactions does on UnClick
AI agents call xero_bank_transactions 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 |
|---|---|---|---|
date_to | string | — | |
date_from | string | — | |
tenant_id | string | — | |
access_token | string | — | |
bank_account_id | string | — |
Parameters from the server's own tool schema.
Why xero_bank_transactions is rated Low
This tool retrieves financial transaction data from Xero accounting software. While it is read-only (no side effects), the elevated severity reflects that financial transaction data is sensitive: unauthorized access could expose account details, transaction history, balances, and other confidential accounting information.
From the tool's definition Tool description states 'Get bank transactions from Xero' - a retrieval operation with no modification, deletion, or execution. The verb 'Get' indicates a read-only query.
Risk signalsHandles credentials or secrets (access_token)
Attacks that exploit this kind of access
The rule that runs xero_bank_transactions 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_bank_transactions, this is the rule to start with:
xero_bank_transactions 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_bank_transactions call is checked against it from then on.
Questions about xero_bank_transactions
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 (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