This record as markdown: /tools/creativelead-unclick/xero-accounts.md
What xero_accounts does on UnClick
AI agents call xero_accounts 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 |
|---|---|---|---|
type | string | — | |
tenant_id | string | — | |
access_token | string | — |
Parameters from the server's own tool schema.
Why xero_accounts is rated Low
This tool retrieves financial account information from Xero (an accounting platform) but does not modify, create, or delete any data. It is a simple read operation with no side effects. While it involves financial systems, it merely queries/retrieves existing data rather than moving money or creating financial obligations, so Financial category does not apply.
From the tool's definition Tool name and description: 'Get chart of accounts from Xero' - uses verb 'Get' which retrieves data without modification. A chart of accounts is a read-only accounting reference structure.
Risk signalsHandles credentials or secrets (access_token)
Attacks that exploit this kind of access
The rule that runs xero_accounts 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_accounts, this is the rule to start with:
xero_accounts 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_accounts call is checked against it from then on.
Questions about xero_accounts
Get chart of accounts from Xero. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
xero_accounts accepts 3 parameters: type, tenant_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_accounts: 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_accounts 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_accounts 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_accounts. 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_accounts 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