granite_withdraw
Withdraw supplied assets plus earned interest
This record as markdown: /tools/stack-ai-mcp-stacks-mcp-server/granite-withdraw.md
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 is rated Critical
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.
Attacks that exploit this kind of access
The rule that runs granite_withdraw safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Stacks AI MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For granite_withdraw, this is the rule to start with:
Any call to granite_withdraw is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Stacks AI MCP Server, apply this rule, and every granite_withdraw call is checked against it from then on.
Questions about granite_withdraw
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.
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.
granite_withdraw 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_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.
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.
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.
More on Stacks AI MCP Server, and thousands of servers like it.
Across the catalogue