list_transactions
Unified history of all money movement: invoice payments, checkout purchases, recurring charges, refunds, and deposit forfeitures.
This record as markdown: /tools/app-businys-mcp-server/list-transactions.md
What list_transactions does on Businys
AI agents call list_transactions to retrieve information from Businys without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_transactions is rated Low
Although this tool exposes sensitive financial data (payments, charges, refunds), it performs only a read operation—retrieving historical transaction records. It does not move money, create charges, or execute financial operations. However, severity is high because unauthorized access to complete transaction histories could enable fraud detection evasion, customer doxing, or business intelligence theft.
From the tool's definition Tool name is 'list_transactions' with description stating it provides 'Unified history of all money movement: invoice payments, checkout purchases, recurring charges, refunds, and deposit forfeitures.' The verb 'list' and 'history' indicate retrieval/querying…
Attacks that exploit this kind of access
The rule that runs list_transactions safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Businys, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_transactions, this is the rule to start with:
list_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 Businys, apply this rule, and every list_transactions call is checked against it from then on.
Questions about list_transactions
Unified history of all money movement: invoice payments, checkout purchases, recurring charges, refunds, and deposit forfeitures. It is categorised as a Read tool in the Businys MCP Server, which means it retrieves data without modifying state.
Register the Businys MCP server in PolicyLayer and add a rule for list_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 Businys. Nothing to install.
list_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_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_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_transactions is provided by the Businys MCP server (@businys/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Businys, and thousands of servers like it.
This server
Across the catalogue