Finalize unstaking after waiting period expires
AI agents use granite_finalize_unstake to commit financial operations through Stacks AI MCP Server — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool moves or commits cryptocurrency by finalizing the return of staked assets. While unstaking returns previously locked funds rather than initiating new obligations, it is irreversible once executed and directly affects financial positions. It ranks as Financial rather than Execute because it specifically handles cryptocurrency/staking operations with direct financial consequences.
From the tool's definition Tool performs 'finalize unstake' on DeFi staking protocol, which commits financial obligations by releasing staked cryptocurrency after a waiting period expires.
Attacks that exploit this kind of access
Finalize unstaking after waiting period expires. It is categorised as a Financial tool in the Stacks AI MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Stacks AI MCP Server MCP server in PolicyLayer and add a rule for granite_finalize_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 Stacks AI MCP Server. Nothing to install.
granite_finalize_unstake 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 granite_finalize_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 granite_finalize_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.
granite_finalize_unstake is provided by the Stacks AI MCP Server MCP server (stack-ai-mcp/stacks-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →