New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

staking_unstakeJupSOL

Unstake jupSOL back to SOL. SAP MCP context: Protocol staking; operation class write. Use for SOL and liquid staking flows. Confirm validator or provider, amount, lockup/unstake terms, and account ownership before writes. Use SAP staking tools for SAP protocol stake accounts; use AgentKit staking...

SERVERSap SOURCEhttps://mcp.sap.oobeprotocol.ai/mcp
Medium RISK CLASS
Category Write
Parameters 22 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/staking-unstakejupsol.md

What staking_unstakeJupSOL does on Sap

AI agents use staking_unstakeJupSOL to create or update resources in Sap, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Sap environment.

ParameterTypeRequiredDescription
amount string Yes Amount of jupSOL to unstake
wallet string Yes Solana public key (base58)

Parameters from the server's own tool schema.

Why staking_unstakeJupSOL is rated Medium

Unstaking modifies staking position and moves token assets, reversibly but with financial impact.

From the tool's definition Unstake jupSOL back to SOL; operation class write

Questions about staking_unstakeJupSOL

What does the staking_unstakeJupSOL tool do? +

Unstake jupSOL back to SOL. SAP MCP context: Protocol staking; operation class write. Use for SOL and liquid staking flows. Confirm validator or provider, amount, lockup/unstake terms, and account ownership before writes. Use SAP staking tools for SAP protocol stake accounts; use AgentKit staking tools for external staking protocols. 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 Write tool in the Sap MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does staking_unstakeJupSOL accept? +

staking_unstakeJupSOL accepts 2 parameters: amount, wallet. Required: amount, wallet. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on staking_unstakeJupSOL? +

Register the Sap MCP server in PolicyLayer and add a rule for staking_unstakeJupSOL: 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 staking_unstakeJupSOL? +

staking_unstakeJupSOL is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit staking_unstakeJupSOL? +

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

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

staking_unstakeJupSOL 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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Sap's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.