Receive Ecash Receive/redeem a Cashu ecash token. The agent swaps the received proofs for new ones at the mint, ensuring the sender can't double-spend. This is the standard Cashu receive flow (NUT-03 swap). Responses: 200: Successful Response (Success Response) Content-Type: application/json
Risk signalsHandles credentials or secrets (token)
Part of the Agent Registry server.
Free to start. No card required.
AI agents use receive_ecash_api_payments_ecash_receive_post to create or modify resources in Agent Registry. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call receive_ecash_api_payments_ecash_receive_post repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Agent Registry.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"receive_ecash_api_payments_ecash_receive_post": {
"limits": [
{
"counter": "receive_ecash_api_payments_ecash_receive_post_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full Agent Registry policy for all 36 tools.
These attack patterns abuse exactly the kind of access receive_ecash_api_payments_ecash_receive_post gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Receive Ecash Receive/redeem a Cashu ecash token. The agent swaps the received proofs for new ones at the mint, ensuring the sender can't double-spend. This is the standard Cashu receive flow (NUT-03 swap). Responses: 200: Successful Response (Success Response) Content-Type: application/json. It is categorised as a Write tool in the Agent Registry MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Agent Registry MCP server in PolicyLayer and add a rule for receive_ecash_api_payments_ecash_receive_post: 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 Agent Registry. Nothing to install.
receive_ecash_api_payments_ecash_receive_post is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the receive_ecash_api_payments_ecash_receive_post 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 receive_ecash_api_payments_ecash_receive_post. 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.
receive_ecash_api_payments_ecash_receive_post is provided by the Agent Registry MCP server (agentry/agent-registry). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 36 Agent Registry tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.