vault_kv_create · HashiCorp Vault MCP Server MCP

WHAT IT DOES

What vault_kv_create does on HashiCorp Vault MCP Server

AI agents use vault_kv_create to create or update resources in HashiCorp Vault MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your HashiCorp Vault MCP Server environment.

WHY IT NEEDS A POLICY

Why vault_kv_create needs a policy

This tool creates new secrets in HashiCorp Vault, which is a reversible operation (secrets can be updated or deleted). It does not execute arbitrary code, delete data irreversibly, or move money. The high severity reflects that misuse could result in creation of unauthorized secrets, credential leakage, or injection of malicious credentials into the vault, affecting systems that depend on those secrets.

From the tool's definition Tool name 'vault_kv_create' and description 'Create a KV secret in HashiCorp Vault at the specified path' explicitly indicate creation of data in a secrets management system.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

vault_kv_create Rate-limited

vault_kv_create stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "vault_kv_create": {
      "limits": [
        {
          "counter": "vault_kv_create_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches HashiCorp Vault MCP Server, so you can run agents against it safely.

FAQ

Questions about vault_kv_create

What does the vault_kv_create tool do? +

Create a KV secret in HashiCorp Vault at the specified path. It is categorised as a Write tool in the HashiCorp Vault MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on vault_kv_create? +

Register the HashiCorp Vault MCP Server MCP server in PolicyLayer and add a rule for vault_kv_create: 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 HashiCorp Vault MCP Server. Nothing to install.

What risk level is vault_kv_create? +

vault_kv_create is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit vault_kv_create? +

Yes. Add a rate_limit block to the vault_kv_create 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.

How do I block vault_kv_create completely? +

Set action: deny in the PolicyLayer policy for vault_kv_create. 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.

What MCP server provides vault_kv_create? +

vault_kv_create is provided by the HashiCorp Vault MCP Server MCP server (rod-anami-kyndryl/hashi-vault-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.