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.
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.
| Parameter | Type | Required | Description |
|---|---|---|---|
url | string | Yes | The toll-booth server URL |
token | string | Yes | Cashu token string to redeem (e.g. cashuAey...) |
Parameters from the server's own tool schema.
This tool redeems ecash tokens (Cashu), which are a form of digital bearer money. Redeeming ecash tokens constitutes a financial operation — it converts monetary value (Cashu tokens) into a credit or payment on a toll-booth server. Misuse could result in unauthorized spending or draining of ecash token balances, placing this firmly in the Financial category with high severity.
From the tool's definition Redeem Cashu ecash tokens directly on a toll-booth server... Handles the two-step flow automatically (create invoice then redeem token)
Risk signalsAccepts URL/endpoint input (url) · Handles credentials or secrets (token)
Documented attack patterns abuse exactly the kind of access l402-redeem-cashu gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and 402, and nothing reaches the server without passing your rules. This is the rule we recommend for l402-redeem-cashu:
{
"version": "1",
"default": "deny",
"tools": {
"l402-redeem-cashu": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
}
}Any call to l402-redeem-cashu is blocked until a human approves it. The rest of the server keeps working.
Free to start. No card required.
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.
l402-redeem-cashu accepts 2 parameters: url, token. Required: url, token. The full parameter table on this page comes from the server's own tool schema.
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.
Start from 402, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
11 402 tools catalogued and risk-classified — across an index of 43,000+ MCP servers.