Get money requests you've sent from a specific account
AI agents call getRequestInquiries 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 queries and retrieves historical money request data from a user's account. It performs a simple read operation on existing payment request records without creating, modifying, deleting, or executing any financial transactions. The severity is low because it only exposes previously-sent request metadata with no ability to move funds or create obligations.
From the tool's definition Tool name 'getRequestInquiries' and description 'Get money requests you've sent from a specific account' indicate a retrieval operation with no modification or execution of financial transactions.
Documented attack patterns abuse exactly the kind of access getRequestInquiries 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 getRequestInquiries:
{
"version": "1",
"default": "deny",
"tools": {
"getRequestInquiries": {}
}
}getRequestInquiries 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.
Get money requests you've sent from 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 getRequestInquiries: 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.
getRequestInquiries 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 getRequestInquiries 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 getRequestInquiries. 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.
getRequestInquiries 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.