Transfer between Kraken wallet types (e.g. Spot ↔ Futures).
AI agents use wallet_transfer to commit financial operations through Mcp Kraken — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool transfers cryptocurrency assets between wallet types on the Kraken exchange, which directly moves financial value and commits crypto holdings to different account states. While reversible (transfers can be undone), it commits financial obligations and moves money, placing it in the Financial category.
From the tool's definition Tool name 'wallet_transfer' and description 'Transfer between Kraken wallet types (e.g. Spot ↔ Futures)' indicates movement of cryptocurrency funds between account types on a cryptocurrency exchange.
Attacks that exploit this kind of access
Transfer between Kraken wallet types (e.g. Spot ↔ Futures). It is categorised as a Financial tool in the Mcp Kraken MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Mcp Kraken MCP server in PolicyLayer and add a rule for wallet_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 Mcp Kraken. Nothing to install.
wallet_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 wallet_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 wallet_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.
wallet_transfer is provided by the Mcp Kraken MCP server (xavierbeheydt/mcp-kraken). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →