identity-setup
Set up a multi-persona identity from the current master secret. Derives named persona sub-identities, optionally creates a Shamir backup and configures relays. Preview mode (confirm: false) shows what would be created without any side effects.
This record as markdown: /tools/dev-forgesworn-bray/identity-setup.md
What identity-setup does on Nostr Bray
AI agents use identity-setup 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-setup is rated Medium
This tool creates and configures identity infrastructure (sub-identities, relay configuration, Shamir backup) from a master secret. It is a Write operation as it establishes new persistent identity state. The severity is high because it handles master secret-derived cryptographic identities — misuse could create rogue personas or misconfigure relays, potentially compromising identity security.
From the tool's definition Set up a multi-persona identity from the current master secret. Derives named persona sub-identities, optionally creates a Shamir backup and configures relays.
Attacks that exploit this kind of access
The rule that runs identity-setup 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-setup, this is the rule to start with:
identity-setup 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-setup call is checked against it from then on.
Questions about identity-setup
Set up a multi-persona identity from the current master secret. Derives named persona sub-identities, optionally creates a Shamir backup and configures relays. Preview mode (confirm: false) shows what would be created without any side effects. 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-setup: 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-setup 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-setup 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-setup. 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-setup 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