View transactions (payments) for a specific account
AI agents call getTransactions to retrieve information from Bunq MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical transaction data without creating, modifying, deleting, or executing any operations. It is purely a query operation on existing financial records. Although the data is sensitive, the action itself is read-only and presents minimal risk compared to tools like createPayment (which would be Financial/Execute) or deleteAccount (which would be Destructive).
From the tool's definition Tool name is 'getTransactions' and description states 'View transactions (payments) for a specific account' — both indicate a retrieval operation with no modification or financial movement.
Documented attack patterns abuse exactly the kind of access getTransactions gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Bunq MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for getTransactions:
{
"version": "1",
"default": "deny",
"tools": {
"getTransactions": {}
}
}getTransactions is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
View transactions (payments) for a specific account. It is categorised as a Read tool in the Bunq MCP MCP Server, which means it retrieves data without modifying state.
Register the Bunq MCP server in PolicyLayer and add a rule for getTransactions: 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 Bunq MCP. Nothing to install.
getTransactions 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 getTransactions 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 getTransactions. 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.
getTransactions is provided by the Bunq MCP server (wilcokruijer/bunq-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Bunq MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
8 Bunq MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.