kv2-list
AI agents call kv2-list to retrieve information from Vault MCP Server (mschuchard) without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
KV v2 list operations retrieve secret metadata or path listings without modifying, executing code, or deleting data. This is characteristic of Read tools. Confidence is slightly reduced due to empty description, but the naming pattern and server context (Vault MCP for secret/policy management) strongly suggest a non-destructive read operation.
From the tool's definition Tool name 'kv2-list' clearly indicates a list operation on KV v2 secrets engine; description is empty but sibling tools like 'audit-devices-list' and 'authentication-engines-list' are also list operations classified as read-only queries.
Attacks that exploit this kind of access
kv2-list. It is categorised as a Read tool in the Vault MCP Server (mschuchard) MCP Server, which means it retrieves data without modifying state.
Register the Vault MCP Server (mschuchard) MCP server in PolicyLayer and add a rule for kv2-list: 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 Server (mschuchard). Nothing to install.
kv2-list 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 kv2-list 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 kv2-list. 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.
kv2-list is provided by the Vault MCP Server (mschuchard) MCP server (mschuchard/vault-mcp-server). 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 →