add_liquidity
Add ETH and token liquidity to create or increase a Uniswap/PancakeSwap liquidity pool position
This record as markdown: /tools/chulanpro5-evm-mcp-server/add-liquidity.md
What add_liquidity does on EVM MCP Server
AI agents use add_liquidity to commit financial operations through EVM MCP Server, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why add_liquidity is rated Critical
This tool commits real financial assets (ETH and tokens) to a liquidity pool on a DEX. It moves funds from the user's wallet into a smart contract position, constituting a financial operation. Misuse could result in significant financial loss through impermanent loss, incorrect pool parameters, or malicious pool interactions.
From the tool's definition Add ETH and token liquidity to create or increase a Uniswap/PancakeSwap liquidity pool position
Attacks that exploit this kind of access
The rule that runs add_liquidity safely
PolicyLayer is an MCP gateway: it sits between your AI agents and EVM MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For add_liquidity, this is the rule to start with:
Any call to add_liquidity is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect EVM MCP Server, apply this rule, and every add_liquidity call is checked against it from then on.
Questions about add_liquidity
Add ETH and token liquidity to create or increase a Uniswap/PancakeSwap liquidity pool position. It is categorised as a Financial tool in the EVM MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the EVM MCP Server 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 EVM MCP Server. Nothing to install.
add_liquidity 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 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 EVM MCP Server MCP server (chulanpro5/evm-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on EVM MCP Server, and thousands of servers like it.
Across the catalogue