This record as markdown: /tools/dev-forgesworn-402-mcp/l402-redeem-cashu.md
What l402-redeem-cashu does on 402
AI agents use l402-redeem-cashu to commit financial operations through 402, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why l402-redeem-cashu is rated Critical
This tool redeems ecash tokens (Cashu) against a toll-booth server, which constitutes a financial transaction — it consumes/transfers digital bearer assets (ecash) in exchange for API access credits. Redeeming ecash tokens is irreversible and directly moves monetary value, placing it firmly in the Financial category. Misuse by an AI agent could result in unauthorized consumption of funds or ecash tokens.
From the tool's definition 'Redeem Cashu ecash tokens', 'avoiding the Lightning round-trip', 'create invoice then redeem token'
Attacks that exploit this kind of access
The rule that runs l402-redeem-cashu safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 402, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For l402-redeem-cashu, this is the rule to start with:
Any call to l402-redeem-cashu is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect 402, apply this rule, and every l402-redeem-cashu call is checked against it from then on.
Questions about l402-redeem-cashu
Redeem Cashu ecash tokens directly on a toll-booth server, avoiding the Lightning round-trip. Handles the two-step flow automatically (create invoice then redeem token). Only works with toll-booth servers. It is categorised as a Financial tool in the 402 MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the 402 MCP server in PolicyLayer and add a rule for l402-redeem-cashu: 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 402. Nothing to install.
l402-redeem-cashu 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 l402-redeem-cashu 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 l402-redeem-cashu. 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.
l402-redeem-cashu is provided by the 402 MCP server (402-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 402, and thousands of servers like it.
Across the catalogue