identity-restore-shamir
Reconstruct a secret from Shamir shard files. Returns the restored npub for verification.
This record as markdown: /tools/dev-forgesworn-bray/identity-restore-shamir.md
What identity-restore-shamir does on Nostr Bray
AI agents invoke identity-restore-shamir to trigger actions in Nostr Bray. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why identity-restore-shamir is rated High
This tool reconstructs a cryptographic secret (likely a private key or seed) from Shamir secret sharing shards. This is an Execute-level operation because it performs cryptographic reconstruction of sensitive key material from multiple inputs. If misused by an AI agent, it could expose a private identity key (nsec), leading to full account compromise — hence high severity.
From the tool's definition Reconstruct a secret from Shamir shard files. Returns the restored npub for verification.
Attacks that exploit this kind of access
The rule that runs identity-restore-shamir 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-shamir, this is the rule to start with:
identity-restore-shamir stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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-shamir call is checked against it from then on.
Questions about identity-restore-shamir
Reconstruct a secret from Shamir shard files. Returns the restored npub for verification. It is categorised as a Execute tool in the Nostr Bray MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Nostr Bray MCP server in PolicyLayer and add a rule for identity-restore-shamir: 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-shamir is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the identity-restore-shamir 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-shamir. 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-shamir 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.
Across the catalogue