search_402_solutions
Search the 402MCP.org registry of HTTP 402 payment solutions (L402, x402, MPP). Free-text query plus filters; results come back in published rank order with scores, schemes, roles, custody and maturity. Call with no arguments to list the whole registry.
This record as markdown: /tools/402mcp-mcp/search-402-solutions.md
What search_402_solutions does on 402mcp
AI agents call search_402_solutions to retrieve information from 402mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
kind | string | — | |
role | string | — | |
limit | integer | — | |
query | string | — | Free text, e.g. 'lightning', 'usdc', 'solana', 'gateway'. |
scheme | string | — | |
mcp_native_only | boolean | — | |
production_only | boolean | — | |
self_custodial_only | boolean | — |
Parameters from the server's own tool schema.
Why search_402_solutions is rated Low
Even though search_402_solutions only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs search_402_solutions safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 402mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For search_402_solutions, this is the rule to start with:
search_402_solutions 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 402mcp, apply this rule, and every search_402_solutions call is checked against it from then on.
Questions about search_402_solutions
Search the 402MCP.org registry of HTTP 402 payment solutions (L402, x402, MPP). Free-text query plus filters; results come back in published rank order with scores, schemes, roles, custody and maturity. Call with no arguments to list the whole registry. It is categorised as a Read tool in the 402mcp MCP Server, which means it retrieves data without modifying state.
search_402_solutions accepts 8 parameters: kind, role, limit, query, scheme, mcp_native_only, production_only, self_custodial_only. The full parameter table on this page comes from the server's own tool schema.
Register the 402 MCP server in PolicyLayer and add a rule for search_402_solutions: 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 402mcp. Nothing to install.
search_402_solutions 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 search_402_solutions 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 search_402_solutions. 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.
search_402_solutions is provided by the 402 MCP server (@402mcp/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