List users in the Xero organization (for expense claims)
AI agents call xero_list_users to retrieve information from Xero Expenses MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves user information from the Xero organization; it does not create, modify, delete, or execute any operations. It is a simple data retrieval function used to support other operations like expense claims. The blast radius of misuse is minimal—an agent could retrieve user lists but cannot perform destructive or financial actions with this tool alone.
From the tool's definition Tool name 'xero_list_users' and description 'List users in the Xero organization' indicate a retrieval/query operation with no modification or side effects. The verb 'list' is explicitly a Read operation.
Attacks that exploit this kind of access
List users in the Xero organization (for expense claims). It is categorised as a Read tool in the Xero Expenses MCP MCP Server, which means it retrieves data without modifying state.
Register the Xero Expenses MCP server in PolicyLayer and add a rule for xero_list_users: 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 Xero Expenses MCP. Nothing to install.
xero_list_users 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_list_users 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_list_users. 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_list_users is provided by the Xero Expenses MCP server (muness/xero-expenses-mcp). 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 →