// SCAN REPORT

Secret Vault MCP Server

11 tools. 5 can modify or destroy data without limits.

1 destructive tool with no built-in limits. Policy required.

Last updated: 2 Jul 2026

5 can modify or destroy data

6 read-only

11 tools total

Community server · catalogue entry verified 02/07/2026

How to control Secret Vault MCP Server ↓

TOOL MAP

What Secret Vault MCP Server exposes to your agents

Read (6) Write / Execute (4) Destructive / Financial (1)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Secret Vault MCP Server tools

Destructive · High vault_delete This tool performs an irreversible operation that destroys stored secrets. Write · High vault_import Import operations write/add data to the vault rather than read or delete it. Write · High vault_set vault_set writes/stores secrets into the encrypted vault, which is a reversible data modification operation. Write · Medium vault_update_tags This tool modifies secret metadata (tags) rather than the secret value itself or deleting data, placing it in the Write category.

5 of Secret Vault MCP Server's 11 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Secret Vault MCP Server

PolicyLayer is an MCP gateway — it sits between your AI agents and Secret Vault MCP Server, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations

{
  "vault_delete": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "vault_import": {
    "limits": [
      {
        "counter": "vault_import_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "vault_exists": {
    "limits": [
      {
        "counter": "vault_exists_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Secret Vault MCP Server — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON SECRET VAULT →

Instant setup, no code required.

FULL CATALOGUE

All 11 Secret Vault MCP Server tools

DESTRUCTIVE 1 tools

Destructive vault_delete Delete a secret from the vault.

WRITE 4 tools

Write vault_import vault_import Write vault_rotate Rotate (replace) an existing secret's value. Write vault_set vault_set Write vault_update_tags Update the tags on a secret without touching its value.

READ 6 tools

Read vault_exists Check whether a secret key exists in the vault. Read vault_get_metadata Get metadata for a secret: tags, created date, last rotated. Read vault_init vault_init Read vault_list List stored secret names and metadata. Values are never returned. Read vault_rekey vault_rekey Read vault_status Check vault status: initialization state, key tier, and secret count.

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Secret Vault MCP Server

Can an AI agent delete data through the Secret Vault MCP Server MCP server? +

Yes. The Secret Vault MCP Server server exposes 1 destructive tools including vault_delete. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Secret Vault MCP Server? +

The Secret Vault MCP Server server has 4 write tools including vault_import, vault_rotate, vault_set. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Secret Vault MCP Server.

How many tools does the Secret Vault MCP Server MCP server expose? +

11 tools across 3 categories: Destructive, Read, Write. 6 are read-only. 5 can modify, create, or delete data.

How do I enforce a policy on Secret Vault MCP Server? +

Register the Secret Vault MCP Server MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Secret Vault MCP Server tool call.

Deterministic rules across all 11 Secret Vault MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON SECRET VAULT →

Instant setup, no code required.

11 Secret Vault MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.