AI agents use verify_transfer to commit financial operations through MBBank MCP Server — usually the final step of a payment, billing, or trading workflow. A call moves real money.
Despite the empty description, the tool name 'verify_transfer' on a banking server with a 'start_transfer' sibling tool indicates this is part of a two-step financial transaction flow. 'Verify' in this context almost certainly means confirming/authorizing a pending transfer, which commits a financial obligation.
From the tool's definition Tool name 'verify_transfer' combined with sibling tool 'start_transfer' on a banking MCP server strongly implies this tool confirms or authorizes a financial transfer operation.
Documented attack patterns abuse exactly the kind of access verify_transfer gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MBBank MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for verify_transfer:
{
"version": "1",
"default": "deny",
"tools": {
"verify_transfer": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
}
} Any call to verify_transfer is blocked until a human approves it. The rest of the server keeps working.
Free to start. No card required.
verify_transfer. It is categorised as a Financial tool in the MBBank MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the MBBank MCP Server MCP server in PolicyLayer and add a rule for verify_transfer: 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 MBBank MCP Server. Nothing to install.
verify_transfer 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 verify_transfer 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 verify_transfer. 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.
verify_transfer is provided by the MBBank MCP Server MCP server (thedtvn/mbbank-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MBBank MCP Server, 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.
11 MBBank MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.