stake_tokens
Stake TNZO tokens as a Validator, ModelProvider, or TeeProvider.
This record as markdown: /tools/network-tenzro-tenzro/stake-tokens.md
What stake_tokens does on Tenzro Ledger MCP
AI agents use stake_tokens to commit financial operations through Tenzro Ledger MCP, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why stake_tokens is rated Critical
Staking tokens commits financial assets (TNZO tokens) to a protocol role, locking them and creating financial obligations/risks. This is a financial operation involving real token assets that could be lost, slashed, or locked for extended periods if misused.
From the tool's definition Stake TNZO tokens as a Validator, ModelProvider, or TeeProvider
Attacks that exploit this kind of access
The rule that runs stake_tokens safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Tenzro Ledger MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For stake_tokens, this is the rule to start with:
Any call to stake_tokens is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Tenzro Ledger MCP, apply this rule, and every stake_tokens call is checked against it from then on.
Questions about stake_tokens
Stake TNZO tokens as a Validator, ModelProvider, or TeeProvider. It is categorised as a Financial tool in the Tenzro Ledger MCP MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Tenzro Ledger MCP server in PolicyLayer and add a rule for stake_tokens: 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 Tenzro Ledger MCP. Nothing to install.
stake_tokens 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 stake_tokens 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 stake_tokens. 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.
stake_tokens is provided by the Tenzro Ledger MCP server (https://canton-mcp.tenzro.network/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Tenzro Ledger, and thousands of servers like it.
Across the catalogue