Add liquidity to Swapsicle pool (creates pool if needed). Auto-wraps TLOS if needed
AI agents invoke swapsicle_add_liquidity to trigger actions in Telos Network MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool executes a blockchain transaction that deposits tokens into a liquidity pool and can create new pools. It triggers external DeFi operations with real financial assets. While it involves financial assets, it is not directly moving money/payments but rather executing a DeFi smart contract interaction.
From the tool's definition Add liquidity to Swapsicle pool (creates pool if needed). Auto-wraps TLOS if needed
Attacks that exploit this kind of access
Add liquidity to Swapsicle pool (creates pool if needed). Auto-wraps TLOS if needed. It is categorised as a Execute tool in the Telos Network MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Telos Network MCP Server MCP server in PolicyLayer and add a rule for swapsicle_add_liquidity: 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 Telos Network MCP Server. Nothing to install.
swapsicle_add_liquidity is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the swapsicle_add_liquidity 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 swapsicle_add_liquidity. 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.
swapsicle_add_liquidity is provided by the Telos Network MCP Server MCP server (tairon-ai/telos-mcp). 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 →