Request 100 testnet TNZO tokens from the faucet (24h cooldown per address).
AI agents use request_faucet to commit financial operations through Tenzro Ledger MCP — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool moves cryptocurrency tokens (TNZO) to a wallet address. Although these are testnet tokens with no direct real-world financial value, the tool operates within a financial/payments infrastructure (wallet, payments, staking context) and involves token issuance mechanics.
From the tool's definition Request 100 testnet TNZO tokens from the faucet
Attacks that exploit this kind of access
Request 100 testnet TNZO tokens from the faucet (24h cooldown per address). 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 request_faucet: 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.
request_faucet 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 request_faucet 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 request_faucet. 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.
request_faucet 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.
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 →