feed-by-name
Fetch recent posts by a contact, searching by name instead of pubkey. Returns an error if zero or multiple contacts match.
This record as markdown: /tools/dev-forgesworn-bray/feed-by-name.md
What feed-by-name does on Nostr Bray
AI agents call feed-by-name 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 feed-by-name is rated Low
This tool retrieves/queries existing data (posts from a contact) based on a search parameter (name). It is a straightforward read operation with no capability to modify, create, delete, or execute external operations. The error handling for zero or multiple matches is informational only and does not change the read-only nature of the operation.
From the tool's definition Tool description states 'Fetch recent posts', which is a retrieval operation with no side effects. Returns data without modifying, creating, or deleting anything.
Attacks that exploit this kind of access
The rule that runs feed-by-name 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 feed-by-name, this is the rule to start with:
feed-by-name 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 feed-by-name call is checked against it from then on.
Questions about feed-by-name
Fetch recent posts by a contact, searching by name instead of pubkey. Returns an error if zero or multiple contacts match. 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 feed-by-name: 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.
feed-by-name 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 feed-by-name 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 feed-by-name. 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.
feed-by-name 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