This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/xero-organisation.md
What xero_organisation does on UnClick
AI agents call xero_organisation 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 |
|---|---|---|---|
tenant_id | string | — | |
access_token | string | — |
Parameters from the server's own tool schema.
Why xero_organisation is rated Low
This tool queries and retrieves organisational information from Xero (accounting software). It performs a read-only operation with no ability to modify, delete, or execute code. While it accesses financial system data, the tool itself only retrieves information and does not move money or commit financial obligations, so it does not qualify as Financial. The blast radius of misuse is limited to information disclosure.
From the tool's definition Tool name 'xero_organisation' with description 'Get organisation details from Xero' — the verb 'Get' indicates data retrieval with no modification or side effects.
Risk signalsHandles credentials or secrets (access_token)
Attacks that exploit this kind of access
The rule that runs xero_organisation 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_organisation, this is the rule to start with:
xero_organisation 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_organisation call is checked against it from then on.
Questions about xero_organisation
Get organisation details from Xero. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
xero_organisation accepts 2 parameters: 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_organisation: 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_organisation 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_organisation 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_organisation. 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_organisation 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.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue