l402-discover
Probe an endpoint to discover its L402 pricing without committing to payment. Returns the cost in sats, available payment methods, and credit tiers (if toll-booth server). The challenge is cached so a subsequent l402-pay can reuse it.
This record as markdown: /tools/dev-forgesworn-402-mcp/l402-discover.md
What l402-discover does on 402
AI agents call l402-discover to retrieve information from 402 without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why l402-discover is rated Low
This tool only probes and retrieves pricing/metadata information from an endpoint without making any payment or commitment. It is a read/discovery operation. The only side effect mentioned is caching the challenge locally, which is benign. Severity is low since misuse only results in information disclosure about pricing structures.
From the tool's definition Probe an endpoint to discover its L402 pricing without committing to payment. Returns the cost in sats, available payment methods, and credit tiers
Attacks that exploit this kind of access
The rule that runs l402-discover 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-discover, this is the rule to start with:
l402-discover is read-only, so it stays allowed. 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-discover call is checked against it from then on.
Questions about l402-discover
Probe an endpoint to discover its L402 pricing without committing to payment. Returns the cost in sats, available payment methods, and credit tiers (if toll-booth server). The challenge is cached so a subsequent l402-pay can reuse it. It is categorised as a Read tool in the 402 MCP Server, which means it retrieves data without modifying state.
Register the 402 MCP server in PolicyLayer and add a rule for l402-discover: 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-discover 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-discover 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-discover. 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-discover 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