sap_adrena_build_remove_liquid_stake
Build an unsigned transaction to remove a liquid stake on Adrena (unstake 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 loca...
This record as markdown: /tools/oobe-protocol-labs-sap-mcp-server/sap-adrena-build-remove-liquid-stake.md
What sap_adrena_build_remove_liquid_stake does on Sap
AI agents invoke sap_adrena_build_remove_liquid_stake 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 | Staker wallet public key (base58). |
amount | number | Yes | Amount of staked LP tokens to withdraw (raw, 6 decimals). |
Parameters from the server's own tool schema.
Why sap_adrena_build_remove_liquid_stake is rated High
Constructs financial transactions for unstaking; requires local signing but initiates value-moving operations with external effects.
From the tool's definition Build unsigned transaction to remove liquid stake on Adrena, unstake LP tokens.
Attacks that exploit this kind of access
The rule that runs sap_adrena_build_remove_liquid_stake 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_remove_liquid_stake, this is the rule to start with:
sap_adrena_build_remove_liquid_stake 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Sap, apply this rule, and every sap_adrena_build_remove_liquid_stake call is checked against it from then on.
Questions about sap_adrena_build_remove_liquid_stake
Build an unsigned transaction to remove a liquid stake on Adrena (unstake 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.
sap_adrena_build_remove_liquid_stake accepts 2 parameters: owner, amount. Required: owner, amount. The full parameter table on this page comes from the server's own tool schema.
Register the Sap MCP server in PolicyLayer and add a rule for sap_adrena_build_remove_liquid_stake: 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.
sap_adrena_build_remove_liquid_stake is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the sap_adrena_build_remove_liquid_stake 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 sap_adrena_build_remove_liquid_stake. 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.
sap_adrena_build_remove_liquid_stake 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.
More on Sap, and thousands of servers like it.
This server
Across the catalogue