Withdraw collateral if health factor allows
AI agents use granite_remove_collateral 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.
Removing collateral from a DeFi lending/borrowing protocol is a financial operation that changes the user's collateral balance and health factor. Misuse could leave positions under-collateralized, trigger liquidations, or drain collateral assets. This falls under Financial as it directly moves assets and affects financial obligations within the DeFi ecosystem.
From the tool's definition 'Withdraw collateral' from a DeFi lending protocol — this moves collateral assets out of a position, directly affecting financial obligations and risk exposure
Attacks that exploit this kind of access
Withdraw collateral if health factor allows. 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_remove_collateral: 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_remove_collateral 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_remove_collateral 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_remove_collateral. 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_remove_collateral 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 →