identity-migrate
Migrate from an old identity to the active one. Shows preview first — set confirm: true to execute. Publishes linkage proof and re-signs migratable events.
This record as markdown: /tools/dev-forgesworn-bray/identity-migrate.md
What identity-migrate does on Nostr Bray
AI agents use identity-migrate 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-migrate is rated Medium
Identity migration creates new linkage proofs and modifies (re-signs) existing events. While it touches identity state, it is fundamentally a Write operation: it creates new cryptographic artifacts and updates event metadata reversibly. This is not Destructive (no data is deleted or overwritten irreversibly), not Execute (no arbitrary code execution), and not Financial.
From the tool's definition Tool description states it 'Publishes linkage proof and re-signs migratable events' — these are creational/modifying operations on Nostr events.
Attacks that exploit this kind of access
The rule that runs identity-migrate 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-migrate, this is the rule to start with:
identity-migrate 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-migrate call is checked against it from then on.
Questions about identity-migrate
Migrate from an old identity to the active one. Shows preview first — set confirm: true to execute. Publishes linkage proof and re-signs migratable events. 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-migrate: 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-migrate 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-migrate 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-migrate. 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-migrate 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