Join pool by specifying exact LP shares to receive
AI agents use join-swap-share-amount-out to commit financial operations through Osmosis MCP Server — usually the final step of a payment, billing, or trading workflow. A call moves real money.
Joining a liquidity pool requires transferring cryptocurrency assets in exchange for LP shares, which constitutes a financial commitment. The tool interacts with DeFi financial instruments on the Osmosis blockchain. Misuse could result in loss of funds or unintended financial exposure, warranting a high severity rating.
From the tool's definition Join pool by specifying exact LP shares to receive — this involves committing funds to a liquidity pool on the Osmosis blockchain, a financial transaction
Attacks that exploit this kind of access
Join pool by specifying exact LP shares to receive. 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 join-swap-share-amount-out: 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.
join-swap-share-amount-out 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 join-swap-share-amount-out 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 join-swap-share-amount-out. 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.
join-swap-share-amount-out 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 →