l402-store-token
Store an L402 token (macaroon:preimage) obtained from a payment page. Use this when a user pastes back a token from a toll-booth payment page. The token is stored as a credential so subsequent l402-fetch calls are authenticated.
This record as markdown: /tools/dev-forgesworn-402-mcp/l402-store-token.md
What l402-store-token does on 402
AI agents use l402-store-token to create or update resources in 402, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your 402 environment.
Why l402-store-token is rated Medium
This tool writes/stores a credential token into local storage. It does not move money itself — the payment has already occurred externally — it merely persists the resulting token for future authenticated requests. This is a reversible write operation (credentials can be deleted/replaced).
From the tool's definition 'Store an L402 token (macaroon:preimage) obtained from a payment page' and 'The token is stored as a credential so subsequent l402-fetch calls are authenticated'
Attacks that exploit this kind of access
The rule that runs l402-store-token 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-store-token, this is the rule to start with:
l402-store-token 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 402, apply this rule, and every l402-store-token call is checked against it from then on.
Questions about l402-store-token
Store an L402 token (macaroon:preimage) obtained from a payment page. Use this when a user pastes back a token from a toll-booth payment page. The token is stored as a credential so subsequent l402-fetch calls are authenticated. It is categorised as a Write tool in the 402 MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the 402 MCP server in PolicyLayer and add a rule for l402-store-token: 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-store-token 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 l402-store-token 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-store-token. 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-store-token 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.
This server
Across the catalogue