vault-create
Create a Dominion vault config with named access tiers. Signs and publishes the config as a kind 30078 event. Returns the created event, publish result, and tier names.
This record as markdown: /tools/dev-forgesworn-bray/vault-create.md
What vault-create does on Nostr Bray
AI agents use vault-create 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 vault-create is rated Medium
This tool creates and publishes a new Nostr event (kind 30078), which modifies the state of a decentralized system by introducing a new vault configuration with access control tiers. This is a Write operation—it creates data reversibly (the vault config can be updated or superseded by publishing new events). It is not Destructive because it does not delete or overwrite existing data irreversibly.
From the tool's definition Tool description states it "Create[s] a Dominion vault config" and "Signs and publishes the config as a kind 30078 event." The action is creating and publishing a new configuration object.
Attacks that exploit this kind of access
The rule that runs vault-create 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-create, this is the rule to start with:
vault-create 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 vault-create call is checked against it from then on.
Questions about vault-create
Create a Dominion vault config with named access tiers. Signs and publishes the config as a kind 30078 event. Returns the created event, publish result, and tier names. 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 vault-create: 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-create 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 vault-create 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-create. 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-create 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