This record as markdown: /tools/dev-forgesworn-bray/verify-event.md
What verify-event does on Nostr Bray
AI agents call verify-event 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 verify-event is rated Low
Verification is a read-only cryptographic validation operation. It retrieves and validates event data without creating, modifying, deleting, or executing external operations. This is a low-risk activity suitable for Read category with low severity since it performs no mutations and has no destructive, financial, or execution implications.
From the tool's definition Tool name 'verify-event' and description 'Verify a Nostr event' indicate a cryptographic verification operation that checks the validity of an existing event without modifying, executing arbitrary code, or causing side effects.
Attacks that exploit this kind of access
The rule that runs verify-event 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 verify-event, this is the rule to start with:
verify-event 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 verify-event call is checked against it from then on.
Questions about verify-event
Verify a Nostr event\. 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 verify-event: 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.
verify-event 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 verify-event 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 verify-event. 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.
verify-event 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