validate-event
Semantically validate an event or unsigned event template against Bray\
This record as markdown: /tools/dev-forgesworn-bray/validate-event.md
What validate-event does on Nostr Bray
AI agents call validate-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 validate-event is rated Low
This tool retrieves and checks the structure/semantics of an event without creating side effects, modifying data, or executing arbitrary operations. It is purely an inspection/query operation, similar to a schema validator. The low severity reflects that validation alone cannot harm data or systems—it only provides feedback about event conformance.
From the tool's definition Tool name 'validate-event' and description indicates it performs semantic validation/checking of events against schema or rules. The verb 'validate' is a read-only verification operation with no modification, deletion, or execution of external operations.
Attacks that exploit this kind of access
The rule that runs validate-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 validate-event, this is the rule to start with:
validate-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 validate-event call is checked against it from then on.
Questions about validate-event
Semantically validate an event or unsigned event template against Bray\. 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 validate-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.
validate-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 validate-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 validate-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.
validate-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