identity-restore
Re-sign migratable events (profile, contacts, relay list) under the active identity. Skips attestations (trust chain protection).
This record as markdown: /tools/dev-forgesworn-bray/identity-restore.md
What identity-restore does on Nostr Bray
AI agents use identity-restore to create or update resources in Nostr Bray, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Nostr Bray environment.
Why identity-restore is rated Medium
The tool modifies (re-signs) existing events under a new identity context. This is a Write operation because it alters data reversibly—the original events can be re-signed again or reverted. While it affects identity and trust infrastructure (which could be sensitive), it does not delete data (ruling out Destructive), execute arbitrary code (Execute), nor move assets (Financial).
From the tool's definition Re-sign migratable events (profile, contacts, relay list) under the active identity. This modifies cryptographic signatures on existing identity-related data structures, which constitutes reversible alteration of data state.
Attacks that exploit this kind of access
The rule that runs identity-restore 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 identity-restore, this is the rule to start with:
identity-restore stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 identity-restore call is checked against it from then on.
Questions about identity-restore
Re-sign migratable events (profile, contacts, relay list) under the active identity. Skips attestations (trust chain protection). It is categorised as a Write tool in the Nostr Bray MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Nostr Bray MCP server in PolicyLayer and add a rule for identity-restore: 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.
identity-restore is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the identity-restore 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 identity-restore. 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.
identity-restore 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