granite_stake
Stake LP tokens to earn additional rewards
This record as markdown: /tools/stack-ai-mcp-stacks-mcp-server/granite-stake.md
What granite_stake does on Stacks AI MCP Server
AI agents use granite_stake 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_stake is rated Critical
Staking LP tokens involves committing financial assets (liquidity provider tokens) to a smart contract to earn rewards. This constitutes a financial commitment on a DeFi protocol, locking up tokens and creating financial obligations/positions. Misuse could result in locked or lost funds, making this a high-severity financial operation.
From the tool's definition Stake LP tokens to earn additional rewards
Attacks that exploit this kind of access
The rule that runs granite_stake 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_stake, this is the rule to start with:
Any call to granite_stake 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_stake call is checked against it from then on.
Questions about granite_stake
Stake LP tokens to earn additional rewards. 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_stake: 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_stake 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_stake 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_stake. 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_stake 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