Add liquidity to a DragonSwap V3 pool
AI agents use add_liquidity to create or update resources in SEI MCP Server V2 — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your SEI MCP Server V2 environment.
This tool modifies blockchain state by creating or updating a liquidity position, making it a Write operation rather than Read. It is not Destructive (the position can be removed/adjusted), not Execute (no arbitrary code execution; the operation is well-defined), and not Financial proper (it doesn't move money for payment/obligation purposes, but rather deploys it within DeFi).
From the tool's definition Tool adds liquidity to a DragonSwap V3 pool, which creates or modifies the user's position in a liquidity pool. The tool name 'add_liquidity' and description indicate a reversible state change to blockchain assets (deposits tokens into a pool).
Attacks that exploit this kind of access
Add liquidity to a DragonSwap V3 pool. It is categorised as a Write tool in the SEI MCP Server V2 MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the SEI MCP Server V2 MCP server in PolicyLayer and add a rule for 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 SEI MCP Server V2. Nothing to install.
add_liquidity is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the 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 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.
add_liquidity is provided by the SEI MCP Server V2 MCP server (testinguser1111111/sei-mcp-server). 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 →