request_faucet
Request testnet TNZO from the faucet (24h cooldown per address).
This record as markdown: /tools/network-tenzro-tenzro/request-faucet.md
What request_faucet does on Tenzro Ledger MCP
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.
Why request_faucet is rated Critical
This tool moves tokens (TNZO) to a wallet address, which is a financial operation. While it operates on testnet tokens (lower real-world value), it still commits a financial transaction by dispensing cryptocurrency. The 24h cooldown per address suggests rate-limiting to prevent abuse.
From the tool's definition Request testnet TNZO from the faucet
Attacks that exploit this kind of access
The rule that runs request_faucet 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 request_faucet, this is the rule to start with:
Any call to request_faucet 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 request_faucet call is checked against it from then on.
Questions about request_faucet
Request testnet TNZO 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.
More on Tenzro Ledger, and thousands of servers like it.
Across the catalogue