add_liquidity_txn

Build unsigned transactions to add liquidity to a Tinyman v2 pool on Algorand. Returns base64-encoded transactions for signing.

Server Tinyman MCP Server nautilusoss/tinymanmcp
Category Financial
Risk class Critical
Parameters 00 required

What add_liquidity_txn does on Tinyman MCP Server

AI agents use add_liquidity_txn to commit financial operations through Tinyman MCP Server — usually the final step of a payment, billing, or trading workflow. A call moves real money.

Why add_liquidity_txn needs a policy

Adding liquidity to a DeFi AMM pool is a financial operation that commits the user's assets (tokens) to a liquidity pool. Although the tool only builds unsigned transactions (the actual signing and submission happen elsewhere), it constructs the financial commitment transactions that, once signed, move funds into the pool.

From the tool's definition 'add liquidity to a Tinyman v2 pool on Algorand' and 'Returns base64-encoded transactions for signing'

Questions about add_liquidity_txn

What does the add_liquidity_txn tool do? +

Build unsigned transactions to add liquidity to a Tinyman v2 pool on Algorand. Returns base64-encoded transactions for signing. It is categorised as a Financial tool in the Tinyman MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

How do I enforce a policy on add_liquidity_txn? +

Register the Tinyman MCP Server MCP server in PolicyLayer and add a rule for add_liquidity_txn: 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 Tinyman MCP Server. Nothing to install.

What risk level is add_liquidity_txn? +

add_liquidity_txn is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit add_liquidity_txn? +

Yes. Add a rate_limit block to the add_liquidity_txn 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.

How do I block add_liquidity_txn completely? +

Set action: deny in the PolicyLayer policy for add_liquidity_txn. 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.

What MCP server provides add_liquidity_txn? +

add_liquidity_txn is provided by the Tinyman MCP Server MCP server (nautilusoss/tinymanmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.