Transfer tokens across chains using IBC
AI agents use ibc-transfer to commit financial operations through Osmosis MCP Server — usually the final step of a payment, billing, or trading workflow. A call moves real money.
IBC (Inter-Blockchain Communication) transfers move tokens across separate blockchain networks. This is a financial operation that results in the permanent movement of cryptocurrency assets from one chain to another. Even though it may be theoretically reversible through a return transfer, the tool itself executes an irreversible financial commitment.
From the tool's definition Tool description states 'Transfer tokens across chains using IBC' - this involves moving cryptocurrency tokens between blockchain networks, which is an irreversible financial transaction that commits actual value transfer obligations.
Attacks that exploit this kind of access
Transfer tokens across chains using IBC. It is categorised as a Financial tool in the Osmosis MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Osmosis MCP Server MCP server in PolicyLayer and add a rule for ibc-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 Osmosis MCP Server. Nothing to install.
ibc-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 ibc-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 ibc-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.
ibc-transfer is provided by the Osmosis MCP Server MCP server (myronkoch-dev/mcp-osmosis). 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 →