Check vault status: initialization state, key tier, and secret count.
AI agents call vault_status to retrieve information from Secret Vault MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs read-only inspection of vault status information. It retrieves the initialization state, key tier information, and a count of secrets—all informational queries with no side effects. The verb 'check' and the focus on state inspection rather than mutation classify it as Read.
From the tool's definition Tool name 'vault_status' and description 'Check vault status: initialization state, key tier, and secret count' indicate a query-only operation that retrieves metadata about vault state without modifying or deleting data.
Attacks that exploit this kind of access
Check vault status: initialization state, key tier, and secret count. It is categorised as a Read tool in the Secret Vault MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Secret Vault MCP Server MCP server in PolicyLayer and add a rule for vault_status: 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 Secret Vault MCP Server. Nothing to install.
vault_status 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_status 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_status. 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_status is provided by the Secret Vault MCP Server MCP server (sam-ueckert/vault-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →