meteora_addDLMMLiquidity

SERVERSap SOURCEhttps://mcp.sap.oobeprotocol.ai/mcp

Critical RISK CLASS

Category Financial

Parameters 74 required

Recommended Approval-gatedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/oobe-protocol-labs-sap-mcp-server/meteora-adddlmmliquidity.md

WHAT IT DOES

What meteora_addDLMMLiquidity does on Sap

AI agents use meteora_addDLMMLiquidity to commit financial operations through Sap, usually the final step of a payment, billing, or trading workflow. A call moves real money.

Parameter	Type	Required	Description
`wallet`	string	Yes	Solana public key (base58)
`amountX`	string	Yes	Raw token amount (smallest unit)
`amountY`	string	Yes	Raw token amount (smallest unit)
`maxBinId`	number	—	Max Bin ID parameter for Meteora Add D L M M Liquidity.
`minBinId`	number	—	Min Bin ID parameter for Meteora Add D L M M Liquidity.
`strategy`	string	—	Liquidity distribution strategy
`poolAddress`	string	Yes	Solana public key (base58)

Parameters from the server's own tool schema.

RISK

Why meteora_addDLMMLiquidity is rated Critical

Adds liquidity to a DeFi pool, committing financial assets to an on-chain protocol.

From the tool's definition Add liquidity to a Meteora DLMM pool with a distribution strategy

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs meteora_addDLMMLiquidity safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Sap, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For meteora_addDLMMLiquidity, this is the rule to start with:

meteora_addDLMMLiquidity Approval-gated

Any call to meteora_addDLMMLiquidity is blocked until a human approves it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "meteora_addDLMMLiquidity": {
      "deny_if": [
        {
          "conditions": [],
          "on_deny": "Requires human approval."
        }
      ]
    }
  }
}

GATE THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Sap, apply this rule, and every meteora_addDLMMLiquidity call is checked against it from then on.

FAQ

Questions about meteora_addDLMMLiquidity

What does the meteora_addDLMMLiquidity tool do? +

Add liquidity to a Meteora DLMM pool with a distribution strategy. SAP MCP context: This Synapse AgentKit tool is served beside the sap_* SDK tools. Use sap_agent_identity_plan, sap_payments_register_agent, sap_payments_update_agent, and sap_publish_tool_by_name when the capability should become part of an on-chain SAP agent profile or tool registry entry. SAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: hosted accountless write is blocked; do not call this as a paid hosted write and no x402 payment should be charged. Use the local sap_payments bridge or a hosted unsigned builder when user signing is required. Signer boundary: user-controlled local profile or external signer; OOBE hosted MCP remains non-custodial. It is categorised as a Financial tool in the Sap MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

What parameters does meteora_addDLMMLiquidity accept? +

meteora_addDLMMLiquidity accepts 7 parameters: wallet, amountX, amountY, maxBinId, minBinId, strategy, poolAddress. Required: wallet, amountX, amountY, poolAddress. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on meteora_addDLMMLiquidity? +

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

What risk level is meteora_addDLMMLiquidity? +

meteora_addDLMMLiquidity 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 meteora_addDLMMLiquidity? +

Yes. Add a rate_limit block to the meteora_addDLMMLiquidity 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 meteora_addDLMMLiquidity completely? +

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

meteora_addDLMMLiquidity is provided by the Sap MCP server (https://mcp.sap.oobeprotocol.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Sap, and thousands of servers like it.

This server

All 375 Sap tools → Critical-risk tools on this server →

Across the catalogue

All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern MCP payment tools →Human-in-the-loop →Tool call approval →