sap_adrena_build_add_locked_stake
Build an unsigned transaction to add a locked stake on Adrena. LP tokens are locked for a specified duration. Returns transactionBase64 only after builder-side RPC simulation passes. Show approval only when safeToApprove=true and approvalBlocked=false; otherwise do not call finalize. SAP MCP exec...
This record as markdown: /tools/oobe-protocol-labs-sap-mcp-server/sap-adrena-build-add-locked-stake.md
What sap_adrena_build_add_locked_stake does on Sap
AI agents use sap_adrena_build_add_locked_stake 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 |
|---|---|---|---|
owner | string | Yes | Staker wallet public key (base58). |
amount | number | Yes | Amount of LP tokens to lock (raw, 6 decimals). |
lockedDays | number | Yes | Lock duration in days. |
Parameters from the server's own tool schema.
Why sap_adrena_build_add_locked_stake is rated Critical
Stakes LP tokens financially, commits assets for a duration; financial obligation with irreversible locking.
From the tool's definition locked stake, LP tokens locked for specified duration, paid builder
Attacks that exploit this kind of access
The rule that runs sap_adrena_build_add_locked_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_add_locked_stake, this is the rule to start with:
Any call to sap_adrena_build_add_locked_stake is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Sap, apply this rule, and every sap_adrena_build_add_locked_stake call is checked against it from then on.
Questions about sap_adrena_build_add_locked_stake
Build an unsigned transaction to add a locked stake on Adrena. LP tokens are locked for a specified duration. Returns transactionBase64 only after builder-side RPC simulation passes. Show approval only when safeToApprove=true and approvalBlocked=false; otherwise do not call finalize. 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 Financial tool in the Sap MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
sap_adrena_build_add_locked_stake accepts 3 parameters: owner, amount, lockedDays. Required: owner, amount, lockedDays. 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_add_locked_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_add_locked_stake 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 sap_adrena_build_add_locked_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_add_locked_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_add_locked_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.
Across the catalogue