This record as markdown: /tools/creativelead-unclick/xero-contacts.md
What xero_contacts does on UnClick
AI agents call xero_contacts 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 |
|---|---|---|---|
search | string | — | |
tenant_id | string | — | |
is_customer | boolean | — | |
is_supplier | boolean | — | |
access_token | string | — |
Parameters from the server's own tool schema.
Why xero_contacts is rated Low
This tool queries and retrieves contact data from Xero accounting software without modifying, creating, or deleting any records. It has no side effects beyond data retrieval. While contacts may contain sensitive information, the risk is mitigated by the read-only nature and the fact that access control is typically enforced at the API/authentication level rather than the tool level.
From the tool's definition Tool name 'xero_contacts' and description 'Get contacts from Xero' indicate a retrieval operation. The verb 'Get' and lack of any modification language (create, update, delete) confirm read-only behavior.
Risk signalsHandles credentials or secrets (access_token)
Attacks that exploit this kind of access
The rule that runs xero_contacts 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_contacts, this is the rule to start with:
xero_contacts 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_contacts call is checked against it from then on.
Questions about xero_contacts
Get contacts from Xero. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
xero_contacts accepts 5 parameters: search, tenant_id, is_customer, is_supplier, 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_contacts: 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_contacts 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_contacts 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_contacts. 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_contacts 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