granite_repay
Repay borrowed stablecoins to reduce debt
This record as markdown: /tools/stack-ai-mcp-stacks-mcp-server/granite-repay.md
What granite_repay does on Stacks AI MCP Server
AI agents use granite_repay 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_repay is rated Critical
This tool makes financial transactions on a DeFi protocol — repaying borrowed stablecoins directly interacts with lending/debt positions on the blockchain. Misuse could result in unintended repayment of funds or manipulation of debt positions, making it a Financial category tool with high severity given the irreversible nature of on-chain transactions.
From the tool's definition Repay borrowed stablecoins to reduce debt
Attacks that exploit this kind of access
The rule that runs granite_repay 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_repay, this is the rule to start with:
Any call to granite_repay 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_repay call is checked against it from then on.
Questions about granite_repay
Repay borrowed stablecoins to reduce debt. 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_repay: 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_repay 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_repay 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_repay. 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_repay 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