listing-search

Search classified listings (NIP-99, kind 30402) by hashtag or geohash location.

SERVERNostr Bray SOURCEnostr-bray

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-bray/listing-search.md

WHAT IT DOES

What listing-search does on Nostr Bray

AI agents call listing-search to retrieve information from Nostr Bray without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why listing-search is rated Low

This tool retrieves and queries existing classified listing data using search parameters. It has no side effects, does not modify data, and does not trigger external operations. The blast radius of misuse is minimal—an agent could potentially spam searches or harvest listing data, but cannot corrupt, delete, or modify the underlying data store. This is a straightforward Read operation.

From the tool's definition Tool description states 'Search classified listings' with filtering by hashtag or geohash location. The verb 'search' combined with read-only filtering indicates retrieval without modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs listing-search safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Nostr Bray, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For listing-search, this is the rule to start with:

listing-search Allowed

listing-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": {
    "listing-search": {}
  }
}

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

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

FAQ

Questions about listing-search

What does the listing-search tool do? +

Search classified listings (NIP-99, kind 30402) by hashtag or geohash location. It is categorised as a Read tool in the Nostr Bray MCP Server, which means it retrieves data without modifying state.

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

Register the Nostr Bray MCP server in PolicyLayer and add a rule for listing-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 Nostr Bray. Nothing to install.

What risk level is listing-search? +

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

Can I rate-limit listing-search? +

Yes. Add a rate_limit block to the listing-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 listing-search completely? +

Set action: deny in the PolicyLayer policy for listing-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 listing-search? +

listing-search is provided by the Nostr Bray MCP server (nostr-bray). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Nostr Bray, and thousands of servers like it.

This server

All 240 Nostr Bray 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 →