Force transfer tokens (admin only)
AI agents use force-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.
This tool moves cryptocurrency tokens, which is a financial operation. The 'force' prefix and 'admin only' restriction indicate it bypasses normal authorization flows, making it extremely dangerous if an AI agent gains access to admin credentials or if the tool is called with unvalidated parameters. Misuse would result in irreversible loss of funds.
From the tool's definition Tool name is 'force-transfer' and description states it 'Force transfer tokens (admin only)'. This directly moves tokens/financial assets on the Osmosis blockchain without standard consent mechanisms.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
Force transfer tokens (admin only). 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 force-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.
force-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 force-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 force-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.
force-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 →