Transfers money between two assets.
AI agents use transfer_create to commit financial operations through Money Manager MCP Server — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool moves money between assets, which is the defining characteristic of Financial category. The critical severity reflects that an AI agent with access to this tool could transfer arbitrary amounts of user funds to unintended recipients, resulting in direct financial loss with minimal recourse. The high confidence is based on unambiguous language in both the tool name and description.
From the tool's definition Tool name 'transfer_create' combined with description 'Transfers money between two assets' directly indicates movement of money between accounts. This is explicitly a financial operation that commits monetary obligations.
Documented attack patterns abuse exactly the kind of access transfer_create gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Money Manager MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for transfer_create:
{
"version": "1",
"default": "deny",
"tools": {
"transfer_create": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
}
} Any call to transfer_create is blocked until a human approves it. The rest of the server keeps working.
Free to start. No card required.
Transfers money between two assets. It is categorised as a Financial tool in the Money Manager MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Money Manager MCP Server MCP server in PolicyLayer and add a rule for transfer_create: 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 Money Manager MCP Server. Nothing to install.
transfer_create 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 transfer_create 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 transfer_create. 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.
transfer_create is provided by the Money Manager MCP Server MCP server (shahlaukik/money-manager-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Money Manager 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.
18 Money Manager MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.