List transactions with filters (date/account/payee/narration/tags/metadata) and pagination.
AI agents call list_transactions to retrieve information from MCP Beancount Tool without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only reads and retrieves transaction data from the Beancount ledger using various filter options. It has no side effects—it does not create, modify, delete, or execute any operations. The parameters are all filter criteria for querying, not for making changes. This is a classic Read operation with minimal risk if misused by an AI agent.
From the tool's definition Tool name is 'list_transactions' and description states it 'List transactions with filters... and pagination.' It retrieves and queries transaction data without modifying or deleting anything.
Attacks that exploit this kind of access
List transactions with filters (date/account/payee/narration/tags/metadata) and pagination. It is categorised as a Read tool in the MCP Beancount Tool MCP Server, which means it retrieves data without modifying state.
Register the MCP Beancount Tool 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 MCP Beancount Tool. 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 MCP Beancount Tool MCP server (onesvat/mcp-beancount). 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 →