Deposit tokens to a governance proposal
AI agents use deposit-proposal to commit financial operations through Osmosis MCP Server — usually the final step of a payment, billing, or trading workflow. A call moves real money.
Depositing tokens to a governance proposal commits financial assets and creates obligations on the blockchain. This is an irreversible financial transaction that moves cryptocurrency value. Even though governance deposits might be recoverable in some blockchain designs, the tool directly facilitates movement of funds, making it Financial rather than merely Write or Execute.
From the tool's definition Tool name 'deposit-proposal' combined with description 'Deposit tokens to a governance proposal' indicates the tool moves tokens (cryptocurrency assets) on the Osmosis blockchain.
Attacks that exploit this kind of access
Deposit tokens to a governance proposal. 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 deposit-proposal: 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.
deposit-proposal 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 deposit-proposal 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 deposit-proposal. 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.
deposit-proposal 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 →