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.
Accepts URL/endpoint input (url); Handles credentials or secrets (token)
Part of the 402 MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call l402-store-token to retrieve information from 402 without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though l402-store-token only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
tools:
l402-store-token:
rules:
- action: allowSee the full 402 policy for all 11 tools.
Agents calling read-class tools like l402-store-token have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.
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 Read tool in the 402 MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for l402-store-token. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the 402 MCP server.
l402-store-token is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the l402-store-token rule in your Intercept 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 Intercept 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). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept