AI agents call vault_status to retrieve information from Vault MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata about credentials (status, last used timestamp, audit count) without creating, modifying, deleting, or executing anything. It is a pure information lookup operation. Severity is low because reading credential metadata poses minimal risk compared to actually using or modifying credentials—it provides visibility without enabling credential compromise or misuse.
From the tool's definition Tool performs only status checks: 'Check the status of a specific credential: active/inactive, last used, audit count.' These are read-only query operations with no modification or side effects.
Attacks that exploit this kind of access
Check the status of a specific credential: active/inactive, last used, audit count. It is categorised as a Read tool in the Vault MCP MCP Server, which means it retrieves data without modifying state.
Register the Vault 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 Vault MCP. 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 Vault MCP server (zerocreds-com/zerocreds-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 →