label-read

Query NIP-32 labels for a target event, pubkey, or address.

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/label-read.md

WHAT IT DOES

What label-read does on Nostr Bray

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

RISK

Why label-read is rated Low

This tool retrieves existing label metadata without modifying, creating, deleting, or executing any operations. It is a passive query operation against a Nostr protocol data structure. No blast radius beyond potential information disclosure of already-public or user-accessible labels.

From the tool's definition Tool name 'label-read' and description 'Query NIP-32 labels' — the verb 'query' combined with 'read' in the name indicates data retrieval only.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

label-read Allowed

label-read 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": {
    "label-read": {}
  }
}

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 label-read call is checked against it from then on.

FAQ

Questions about label-read

What does the label-read tool do? +

Query NIP-32 labels for a target event, pubkey, or address. 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 label-read? +

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

What risk level is label-read? +

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

Can I rate-limit label-read? +

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

How do I block label-read completely? +

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

What MCP server provides label-read? +

label-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.

KEEP EXPLORING

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

This server

All 240 Nostr Bray tools →

Across the catalogue

claude_read_file on Claude Bridge → The MCP Attack Database →

Guides

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