vault-config
Fetch a vault config and return a summary of tier names, member counts, revoked count, grant count, and current epoch. Optionally inspect another author\
This record as markdown: /tools/dev-forgesworn-bray/vault-config.md
What vault-config does on Nostr Bray
AI agents call vault-config 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 vault-config is rated Low
This tool retrieves and summarizes configuration data about vaults (tier names, member counts, revoked count, grant count, current epoch). It performs no write, delete, execute, or financial operations. The 'optionally inspect another author' clause does not change this—inspection is a read operation.
From the tool's definition Tool description: 'Fetch a vault config and return a summary...' The verb 'Fetch' and the action of returning a summary indicate data retrieval with no modification. The optional inspection of another author is still a read-only query operation.
Attacks that exploit this kind of access
The rule that runs vault-config 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-config, this is the rule to start with:
vault-config 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 vault-config call is checked against it from then on.
Questions about vault-config
Fetch a vault config and return a summary of tier names, member counts, revoked count, grant count, and current epoch. Optionally inspect another author\. 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 vault-config: 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-config 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 vault-config 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-config. 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-config 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