kv2-update-metadata · Vault MCP Server (mschuchard) MCP

WHAT IT DOES

What kv2-update-metadata does on Vault MCP Server (mschuchard)

AI agents use kv2-update-metadata 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.

WHY IT NEEDS A POLICY

Why kv2-update-metadata needs a policy

This tool modifies metadata for KV v2 secrets in Vault. Metadata updates are reversible writes that can affect secret properties (TTL, version retention, visibility settings) without permanently destroying data. Categorized as Write rather than Read (performs modification), Execute (no arbitrary code execution implied), or Destructive (metadata updates are typically reversible).

From the tool's definition Tool name 'kv2-update-metadata' indicates modification of KV v2 secret engine metadata in HashiCorp Vault. The 'update' verb in the name directly implies write/modification operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

kv2-update-metadata Rate-limited

kv2-update-metadata 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": {
    "kv2-update-metadata": {
      "limits": [
        {
          "counter": "kv2-update-metadata_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 Vault MCP Server (mschuchard), so you can run agents against it safely.

FAQ

Questions about kv2-update-metadata

What does the kv2-update-metadata tool do? +

kv2-update-metadata. 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.

How do I enforce a policy on kv2-update-metadata? +

Register the Vault MCP Server (mschuchard) MCP server in PolicyLayer and add a rule for kv2-update-metadata: 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.

What risk level is kv2-update-metadata? +

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

Can I rate-limit kv2-update-metadata? +

Yes. Add a rate_limit block to the kv2-update-metadata 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 kv2-update-metadata completely? +

Set action: deny in the PolicyLayer policy for kv2-update-metadata. 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 kv2-update-metadata? +

kv2-update-metadata 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.