sap_adrena_build_add_liquidity

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

High RISK CLASS

Category Execute

Parameters 53 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/oobe-protocol-labs-sap-mcp-server/sap-adrena-build-add-liquidity.md

WHAT IT DOES

What sap_adrena_build_add_liquidity does on Sap

AI agents invoke sap_adrena_build_add_liquidity to trigger actions in Sap. 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.

Parameter	Type	Required	Description
`owner`	string	Yes	Liquidity provider wallet public key (base58).
`amount`	number	Yes	Amount in human-readable units.
`poolName`	string	—	Pool to add liquidity to.
`minLpAmountOut`	number	—	Minimum LP tokens to receive (raw). 0 for no slippage protection.
`collateralToken`	string	Yes	Collateral token to deposit.

Parameters from the server's own tool schema.

RISK

Why sap_adrena_build_add_liquidity is rated High

sap_adrena_build_add_liquidity triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs sap_adrena_build_add_liquidity 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 sap_adrena_build_add_liquidity, this is the rule to start with:

sap_adrena_build_add_liquidity Rate-limited

sap_adrena_build_add_liquidity stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "sap_adrena_build_add_liquidity": {
      "limits": [
        {
          "counter": "sap_adrena_build_add_liquidity_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about sap_adrena_build_add_liquidity

What does the sap_adrena_build_add_liquidity tool do? +

Build an unsigned transaction to add liquidity to an Adrena pool. Deposits collateral and receives LP tokens. Returns transactionBase64 for local signing. SAP MCP execution guidance: Intent: hosted unsigned transaction builder. Pricing: paid builder; estimate first, then pay/build and finalize unsigned transactions locally when returned. Routing: paid hosted call; call sap_estimate_tool_cost first, then use sap_payments_call_paid_tool if the runtime cannot handle x402 natively. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required. It is categorised as a Execute tool in the Sap MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

What parameters does sap_adrena_build_add_liquidity accept? +

sap_adrena_build_add_liquidity accepts 5 parameters: owner, amount, poolName, minLpAmountOut, collateralToken. Required: owner, amount, collateralToken. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on sap_adrena_build_add_liquidity? +

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

What risk level is sap_adrena_build_add_liquidity? +

sap_adrena_build_add_liquidity is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit sap_adrena_build_add_liquidity? +

Yes. Add a rate_limit block to the sap_adrena_build_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.

How do I block sap_adrena_build_add_liquidity completely? +

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

What MCP server provides sap_adrena_build_add_liquidity? +

sap_adrena_build_add_liquidity 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 → High-risk tools on this server →

Across the catalogue

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

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →