addLiquidity
Inject funds into a Liquidity Mining pool.\n\n-
This record as markdown: /tools/bybit-exchange-trading-mcp/addliquidity.md
What addLiquidity does on Bybit MCP Server
AI agents use addLiquidity to commit financial operations through Bybit MCP Server, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why addLiquidity is rated Critical
This tool moves cryptocurrency funds into a liquidity mining pool, which is a direct financial commitment of assets. Misuse could result in irreversible or hard-to-reverse financial losses on a live cryptocurrency exchange.
From the tool's definition "Inject funds into a Liquidity Mining pool"
Attacks that exploit this kind of access
The rule that runs addLiquidity safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Bybit MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For addLiquidity, this is the rule to start with:
Any call to addLiquidity is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Bybit MCP Server, apply this rule, and every addLiquidity call is checked against it from then on.
Questions about addLiquidity
Inject funds into a Liquidity Mining pool.\n\n-. It is categorised as a Financial tool in the Bybit MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Bybit MCP Server MCP server in PolicyLayer and add a rule for addLiquidity: 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 Bybit MCP Server. Nothing to install.
addLiquidity 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 addLiquidity 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 addLiquidity. 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.
addLiquidity is provided by the Bybit MCP Server MCP server (bybit-exchange/trading-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Bybit MCP Server, and thousands of servers like it.
Across the catalogue