kv2-create-or-update
AI agents use kv2-create-or-update to create or update resources in Vault MCP Server (mschuchard) — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Vault MCP Server (mschuchard) environment.
This tool creates or updates secrets in Vault's KV v2 secret engine, which is a reversible write operation. It could allow an AI agent to store or overwrite sensitive data (credentials, API keys, tokens), making it high-severity due to potential exposure or disruption of secret material.
From the tool's definition Tool name 'kv2-create-or-update' indicates creation or modification of KV v2 secrets in HashiCorp Vault. The server description confirms it provides tools for 'secret engines like KV v2'.
Attacks that exploit this kind of access
kv2-create-or-update. It is categorised as a Write tool in the Vault MCP Server (mschuchard) MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Vault MCP Server (mschuchard) MCP server in PolicyLayer and add a rule for kv2-create-or-update: 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-create-or-update is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the kv2-create-or-update 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-create-or-update. 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-create-or-update 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 →