store-routing-credentials
Store L402 payment credentials (macaroon + preimage) after paying a routing invoice.
This record as markdown: /tools/dev-forgesworn-rendezvous-mcp/store-routing-credentials.md
What store-routing-credentials does on Rendezvous
AI agents use store-routing-credentials to create or update resources in Rendezvous, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Rendezvous environment.
Why store-routing-credentials is rated Medium
This tool stores sensitive cryptographic payment credentials (macaroon + preimage) derived from a Lightning Network L402 payment flow. The act of storing these credentials is a Write operation (creating/persisting data). However, because it involves payment-related credentials (preimage proves payment, macaroon grants access post-payment), it sits at the boundary of Financial and Write.
From the tool's definition Store L402 payment credentials (macaroon + preimage) after paying a routing invoice
Attacks that exploit this kind of access
The rule that runs store-routing-credentials safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Rendezvous, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For store-routing-credentials, this is the rule to start with:
store-routing-credentials stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Rendezvous, apply this rule, and every store-routing-credentials call is checked against it from then on.
Questions about store-routing-credentials
Store L402 payment credentials (macaroon + preimage) after paying a routing invoice. It is categorised as a Write tool in the Rendezvous MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Rendezvous MCP server in PolicyLayer and add a rule for store-routing-credentials: 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 Rendezvous. Nothing to install.
store-routing-credentials 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 store-routing-credentials 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 store-routing-credentials. 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.
store-routing-credentials is provided by the Rendezvous MCP server (rendezvous-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Rendezvous, and thousands of servers like it.
This server
Across the catalogue