list_xero_bank_transactions
List LIVE bank transactions from the company's connected Xero ledger (paged, 100 per page, newest first). Use for "current bank activity", reconciliation questions, or verifying a specific payment hit the bank. Routing: LIVE bank transactions from Xero (newest first) → use for current bank activi...
This record as markdown: /tools/com-getfreedomos-freedom-mcp/list-xero-bank-transactions.md
What list_xero_bank_transactions does on Freedom Mcp
AI agents call list_xero_bank_transactions to retrieve information from Freedom Mcp 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 |
|---|---|---|---|
page | number | — | Page number, 1-based (Xero pages at 100). Default 1. |
companyId | string | Yes | FreedomOS company id to act within (you must be a member). Required for company-scoped tools. |
from_date | string | — | Only transactions on/after this date, YYYY-MM-DD |
Parameters from the server's own tool schema.
Why list_xero_bank_transactions is rated Low
This is a Read operation: it queries and retrieves financial transaction data without side effects. However, the severity is high rather than low because the data accessed is sensitive financial information (live bank transactions, payment details) that could enable fraud detection evasion, account reconciliation manipulation, or exposure of confidential cash flow information if an AI agent were compromised or…
From the tool's definition Tool retrieves LIVE bank transactions from the company's connected Xero ledger. Description explicitly states it lists transactions for reviewing 'current bank activity' and 'verifying a specific payment hit the bank.' No modification, deletion, or execution…
Attacks that exploit this kind of access
The rule that runs list_xero_bank_transactions safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Freedom Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_xero_bank_transactions, this is the rule to start with:
list_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 Freedom Mcp, apply this rule, and every list_xero_bank_transactions call is checked against it from then on.
Questions about list_xero_bank_transactions
List LIVE bank transactions from the company's connected Xero ledger (paged, 100 per page, newest first). Use for "current bank activity", reconciliation questions, or verifying a specific payment hit the bank. Routing: LIVE bank transactions from Xero (newest first) → use for current bank activity questions. It is categorised as a Read tool in the Freedom Mcp MCP Server, which means it retrieves data without modifying state.
list_xero_bank_transactions accepts 3 parameters: page, companyId, from_date. Required: companyId. The full parameter table on this page comes from the server's own tool schema.
Register the Freedom MCP server in PolicyLayer and add a rule for list_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 Freedom Mcp. Nothing to install.
list_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 list_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 list_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.
list_xero_bank_transactions is provided by the Freedom MCP server (https://twuluxmoognlwtmaoqgo.supabase.co/functions/v1/freedom-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Freedom, and thousands of servers like it.
This server
Across the catalogue