group-info
Fetch group metadata (name, about, picture) for a NIP-29 group.
This record as markdown: /tools/dev-forgesworn-bray/group-info.md
What group-info does on Nostr Bray
AI agents call group-info 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 group-info is rated Low
This tool retrieves group information from a Nostr NIP-29 group without creating, modifying, deleting, or executing any operations. The verb 'Fetch' and the scope (metadata only) confirm it is a Read operation with minimal blast radius if misused by an AI agent.
From the tool's definition Tool name 'group-info' and description 'Fetch group metadata' indicate a retrieval operation with no mutation or side effects. The metadata fields listed (name, about, picture) are read-only attributes.
Attacks that exploit this kind of access
The rule that runs group-info 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 group-info, this is the rule to start with:
group-info 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 group-info call is checked against it from then on.
Questions about group-info
Fetch group metadata (name, about, picture) for a NIP-29 group. 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 group-info: 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.
group-info 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 group-info 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 group-info. 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.
group-info 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