AI agents use start_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.
A tool that starts financial transfers commits financial obligations and moves money. This is the most severe category (Financial > Destructive > Execute > Write > Read). Even though the description is empty, the function name combined with the server's explicit banking context and presence of verify_transfer as a sibling tool makes the intent unambiguous.
From the tool's definition Tool name is 'start_transfer' on an MBBank server with description stating it 'providing monitoring and analytics capabilities for MBBank accounts.' Sibling tools include transaction and balance queries, indicating this server manages real financial accounts.
Documented attack patterns abuse exactly the kind of access start_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 start_transfer:
{
"version": "1",
"default": "deny",
"tools": {
"start_transfer": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
}
} Any call to start_transfer is blocked until a human approves it. The rest of the server keeps working.
Free to start. No card required.
start_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 start_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.
start_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 start_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 start_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.
start_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.