search-profiles

Search for Nostr profiles (kind 0) by keyword using NIP-50. Requires relay support for NIP-50 — if results are empty, try relay-info to check NIP support.

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

WHAT IT DOES

What search-profiles does on Nostr Bray

AI agents call search-profiles 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 search-profiles is rated Low

This tool queries existing data (Nostr profile metadata) and returns results. There is no creation, modification, deletion, code execution, or financial action. It is a straightforward read/search operation with minimal risk — the worst case is an AI agent fetching irrelevant profile data or consuming relay bandwidth.

From the tool's definition Tool description states it "search[es] for Nostr profiles", which is a retrieval operation with no side effects. The mechanism is a keyword search query against relay data (NIP-50), returning matching profiles.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

search-profiles Allowed

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

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

FAQ

Questions about search-profiles

What does the search-profiles tool do? +

Search for Nostr profiles (kind 0) by keyword using NIP-50. Requires relay support for NIP-50 — if results are empty, try relay-info to check NIP support. 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 search-profiles? +

Register the Nostr Bray MCP server in PolicyLayer and add a rule for search-profiles: 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 search-profiles? +

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

Can I rate-limit search-profiles? +

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

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

search-profiles 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 →