vault-revoke
Revoke a pubkey from the vault config. Fetches the current config, adds the pubkey to the revoked list, signs, and republishes the updated config event. Returns the updated event and revoked npub.
This record as markdown: /tools/dev-forgesworn-bray/vault-revoke.md
What vault-revoke does on Nostr Bray
AI agents call vault-revoke to permanently remove resources in Nostr Bray, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why vault-revoke is rated Critical
Revoking a pubkey is an irreversible access-control action that permanently denies a key's access to the vault. While the config event is republished (suggesting some form of state update), the revocation itself is a destructive act — once revoked, the pubkey loses access and this cannot be automatically undone without a deliberate re-grant.
From the tool's definition Revoke a pubkey from the vault config... adds the pubkey to the revoked list... republishes the updated config event
Attacks that exploit this kind of access
The rule that runs vault-revoke 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 vault-revoke, this is the rule to start with:
vault-revoke is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Nostr Bray, apply this rule, and every vault-revoke call is checked against it from then on.
Questions about vault-revoke
Revoke a pubkey from the vault config. Fetches the current config, adds the pubkey to the revoked list, signs, and republishes the updated config event. Returns the updated event and revoked npub. It is categorised as a Destructive tool in the Nostr Bray MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Nostr Bray MCP server in PolicyLayer and add a rule for vault-revoke: 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.
vault-revoke is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the vault-revoke 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 vault-revoke. 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.
vault-revoke 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