List available credential handles. You will never see the credential values — only the handle, label, and type.
AI agents call vault_handles to retrieve information from Kova Mind MCP Server 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 stored credentials (handles, labels, types) without exposing sensitive values or modifying any state. It poses minimal risk as an attacker could only discover what credentials exist, not access their values. Classification as Read is appropriate for inventory/discovery operations with no mutation or execution capability.
From the tool's definition Tool description explicitly states it 'List[s] available credential handles' and 'You will never see the credential values — only the handle, label, and type.' The verb 'list' and the clarification that values are not exposed indicate a read-only operation…
Attacks that exploit this kind of access
List available credential handles. You will never see the credential values — only the handle, label, and type. It is categorised as a Read tool in the Kova Mind MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Kova Mind MCP Server MCP server in PolicyLayer and add a rule for vault_handles: 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 Kova Mind MCP Server. Nothing to install.
vault_handles 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_handles 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_handles. 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_handles is provided by the Kova Mind MCP Server MCP server (kovamind/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
vault_handles is one line of Kova Mind MCP Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →