sap_complete_unstake
Complete unstake for an agent wallet. SAP MCP context: SAP protocol staking flow. Confirm agent wallet, amount, and unstake timing before writes; this is distinct from external AgentKit staking protocol tools. SAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid read-premium; ...
This record as markdown: /tools/oobe-protocol-labs-sap-mcp-server/sap-complete-unstake.md
What sap_complete_unstake does on Sap
AI agents use sap_complete_unstake 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
agentWallet | string | — | Agent wallet public key (base58) to complete unstaking for |
Parameters from the server's own tool schema.
Why sap_complete_unstake is rated Medium
Modifies staking position irreversibly by completing unstake; high financial impact but reversible via re-staking.
From the tool's definition Complete unstake for an agent wallet; writes staking state; agent wallet confirmation required.
Attacks that exploit this kind of access
The rule that runs sap_complete_unstake 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_complete_unstake, this is the rule to start with:
sap_complete_unstake stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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_complete_unstake call is checked against it from then on.
Questions about sap_complete_unstake
Complete unstake for an agent wallet. SAP MCP context: SAP protocol staking flow. Confirm agent wallet, amount, and unstake timing before writes; this is distinct from external AgentKit staking protocol tools. 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: 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 Write tool in the Sap MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
sap_complete_unstake accepts 1 parameter: agentWallet. 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_complete_unstake: 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_complete_unstake is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the sap_complete_unstake 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_complete_unstake. 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_complete_unstake 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