l402-search

Search for paid APIs and services. Use this when the user wants something that might be available as a paid service — jokes, data, AI, content, etc. Discovers services announced on Nostr and returns their URLs, pricing, and capabilities. Then use l402-fetch with the URL to access the service.

SERVER402 SOURCE402-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/dev-forgesworn-402-mcp/l402-search.md

WHAT IT DOES

What l402-search does on 402

AI agents call l402-search 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.

RISK

Why l402-search is rated Low

This tool retrieves and queries data about available services from Nostr announcements, returning metadata (URLs, pricing, capabilities). However, severity is elevated from 'low' to 'medium' because the context shows this server enables autonomous financial operations (sibling tools include l402-pay, l402-buy-credits).

From the tool's definition Tool description states it 'Search for paid APIs and services' and 'Discovers services announced on Nostr and returns their URLs, pricing, and capabilities.' The verb 'search' and 'discover' indicate information retrieval with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs l402-search 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-search, this is the rule to start with:

l402-search Allowed

l402-search is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "l402-search": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect 402, apply this rule, and every l402-search call is checked against it from then on.

FAQ

Questions about l402-search

What does the l402-search tool do? +

How do I enforce a policy on l402-search? +

Register the 402 MCP server in PolicyLayer and add a rule for l402-search: 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.

What risk level is l402-search? +

l402-search is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit l402-search? +

Yes. Add a rate_limit block to the l402-search 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.

How do I block l402-search completely? +

Set action: deny in the PolicyLayer policy for l402-search. 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.

What MCP server provides l402-search? +

l402-search 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.

KEEP EXPLORING

More on 402, and thousands of servers like it.

This server

All 10 402 tools →

Across the catalogue

search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server →search_channel on YouTube MCP Server →hybrid_search on Azure AI Agent Service + Azure AI Search MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →