listing-read
Read classified listing(s) (NIP-99, kind 30402) by author and optional slug.
This record as markdown: /tools/dev-forgesworn-bray/listing-read.md
What listing-read does on Nostr Bray
AI agents call listing-read 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.
Why listing-read is rated Low
This tool only retrieves or queries existing classified listing data from a Nostr protocol (NIP-99, kind 30402). It performs no modifications, deletions, or external operations. The 'Read' category is appropriate, with low severity due to minimal blast radius—the worst case is information disclosure of already-published listings.
From the tool's definition Tool name is 'listing-read' and description explicitly states 'Read classified listing(s)' with no modifications or side effects. Retrieves data by author and slug parameters.
Attacks that exploit this kind of access
The rule that runs listing-read 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-read, this is the rule to start with:
listing-read 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 Nostr Bray, apply this rule, and every listing-read call is checked against it from then on.
Questions about listing-read
Read classified listing(s) (NIP-99, kind 30402) by author and optional slug. It is categorised as a Read tool in the Nostr Bray MCP Server, which means it retrieves data without modifying state.
Register the Nostr Bray MCP server in PolicyLayer and add a rule for listing-read: 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.
listing-read 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 listing-read 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 listing-read. 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.
listing-read 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.
More on Nostr Bray, and thousands of servers like it.
This server
Across the catalogue