verify-person
Verify a Nostr identity: checks NIP-05, trust score, kind 31000 attestations, linkage proofs, and (in full mode) ring endorsements and a spoken challenge token. Accepts any identifier: name, NIP-05, npub, or hex pubkey.
This record as markdown: /tools/dev-forgesworn-bray/verify-person.md
What verify-person does on Nostr Bray
AI agents call verify-person 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-person is rated Low
This is a Read operation: it retrieves and validates identity attributes (NIP-05, trust scores, attestations, proofs, endorsements, challenge tokens) without side effects. However, severity is high because in a trust-aware system, a compromised verify tool could be exploited to impersonate verified identities or access trust-gated resources by returning false positive verifications.
From the tool's definition Tool description indicates it 'checks' and 'verifies' identity information—operations that retrieve and query data without modifying it. Key verbs: 'checks NIP-05', 'trust score', 'attestations', 'linkage proofs', 'ring endorsements'.
Attacks that exploit this kind of access
The rule that runs verify-person 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-person, this is the rule to start with:
verify-person 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-person call is checked against it from then on.
Questions about verify-person
Verify a Nostr identity: checks NIP-05, trust score, kind 31000 attestations, linkage proofs, and (in full mode) ring endorsements and a spoken challenge token. 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 verify-person: 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-person 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-person 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-person. 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-person 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