social-notifications
Fetch notifications for the active identity — mentions, replies, reactions, and zap receipts.
This record as markdown: /tools/dev-forgesworn-bray/social-notifications.md
What social-notifications does on Nostr Bray
AI agents call social-notifications 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 social-notifications is rated Low
This tool retrieves notification data for the user without modifying, executing external operations, or destructing any data. It is a straightforward read operation. Severity is low because notification data itself is typically non-sensitive metadata, and fetching it carries minimal blast radius even if an agent misuses it (at worst, unauthorized access to the user's own notification feed).
From the tool's definition Tool name and description indicate 'Fetch notifications' — a retrieval operation with no side effects. The description lists only passive data retrieval (mentions, replies, reactions, zap receipts).
Attacks that exploit this kind of access
The rule that runs social-notifications 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 social-notifications, this is the rule to start with:
social-notifications 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 social-notifications call is checked against it from then on.
Questions about social-notifications
Fetch notifications for the active identity — mentions, replies, reactions, and zap receipts. 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 social-notifications: 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.
social-notifications 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 social-notifications 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 social-notifications. 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.
social-notifications 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