article-read
Read long-form article(s) (NIP-23, kind 30023) by author. Optionally fetch a specific article by slug. Accepts any identifier: name, NIP-05, npub, or hex pubkey.
This record as markdown: /tools/dev-forgesworn-bray/article-read.md
What article-read does on Nostr Bray
AI agents call article-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 article-read is rated Low
This tool retrieves data from Nostr (long-form articles via NIP-23) without any side effects. It accepts query parameters (author identifier, optional slug) to retrieve existing content. This is a pure read operation with minimal blast radius if misused—an agent could only retrieve articles an author has published, not modify or delete them.
From the tool's definition Tool name is 'article-read' and description explicitly states 'Read long-form article(s)' with fetch operations. No modifications, deletions, or external state changes occur.
Attacks that exploit this kind of access
The rule that runs article-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 article-read, this is the rule to start with:
article-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 article-read call is checked against it from then on.
Questions about article-read
Read long-form article(s) (NIP-23, kind 30023) by author. Optionally fetch a specific article by slug. Accepts any identifier: name, NIP-05, npub, or hex pubkey. 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 article-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.
article-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 article-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 article-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.
article-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