This record as markdown: /tools/dev-forgesworn-bray/identity-backup-shamir.md
What identity-backup-shamir does on Nostr Bray
AI agents call identity-backup-shamir 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 identity-backup-shamir is rated Low
Shamir secret sharing splits a secret (likely a private key or identity credential) into shares. This is primarily a cryptographic read/export operation on sensitive identity data. It does not delete the identity but does export highly sensitive key material. Since the description is truncated, confidence is reduced.
From the tool's definition 'Split the active identity' — description is truncated/uninformative beyond indicating a Shamir secret sharing operation on identity data
Attacks that exploit this kind of access
The rule that runs identity-backup-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-backup-shamir, this is the rule to start with:
identity-backup-shamir 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 identity-backup-shamir call is checked against it from then on.
Questions about identity-backup-shamir
Split the active identity\. 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 identity-backup-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-backup-shamir 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 identity-backup-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-backup-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-backup-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.
This server
Across the catalogue