Create draft payments with optional scheduling (requires review / approval in
AI agents use createDraftPayment to commit financial operations through Bunq MCP — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool creates draft payments in a banking context. Even though it requires review/approval before final execution, it initiates a financial transaction workflow and commits financial intent. Given the banking API context (Bunq), misuse could result in unauthorized payment initiation.
From the tool's definition "Create draft payments" — involves initiating payment transactions through the Bunq banking API, even if requiring approval before execution
Documented attack patterns abuse exactly the kind of access createDraftPayment 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 createDraftPayment:
{
"version": "1",
"default": "deny",
"tools": {
"createDraftPayment": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
}
} Any call to createDraftPayment is blocked until a human approves it. The rest of the server keeps working.
Free to start. No card required.
Create draft payments with optional scheduling (requires review / approval in. It is categorised as a Financial tool in the Bunq MCP MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Bunq MCP server in PolicyLayer and add a rule for createDraftPayment: 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.
createDraftPayment is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the createDraftPayment 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 createDraftPayment. 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.
createDraftPayment 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.