granite_withdraw

Withdraw supplied assets plus earned interest

Server Stacks AI MCP Server stack-ai-mcp/stacks-mcp-server
Category Financial
Risk class Critical
Parameters 00 required

What granite_withdraw does on Stacks AI MCP Server

AI agents use granite_withdraw 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.

Why granite_withdraw needs a policy

This tool directly moves money (cryptocurrency assets and earned interest) from a smart contract back to a user's wallet. It commits financial obligations and transfers value, matching the Financial category definition of 'moves money or commits financial obligations.' While the specific user initiating the withdrawal should theoretically be the owner of those assets, an AI agent with access to this tool could…

From the tool's definition The tool "granite_withdraw" is described as enabling withdrawal of "supplied assets plus earned interest" from what appears to be a lending protocol (Granite) on the Stacks DeFi ecosystem. This involves moving cryptocurrency assets and accrued financial gains.

Questions about granite_withdraw

What does the granite_withdraw tool do? +

Withdraw supplied assets plus earned interest. 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.

How do I enforce a policy on granite_withdraw? +

Register the Stacks AI MCP Server MCP server in PolicyLayer and add a rule for granite_withdraw: 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.

What risk level is granite_withdraw? +

granite_withdraw is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit granite_withdraw? +

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

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

granite_withdraw 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.