// SCAN REPORT

Psamvault

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

4 write tools that can modify data. Rate limits recommended.

Last updated: 30 Jun 2026

4 can modify or destroy data

7 read-only

11 tools total

Community server · catalogue entry verified 30/06/2026

How to control Psamvault ↓

TOOL MAP

What Psamvault exposes to your agents

Read (7) Write / Execute (4) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous Psamvault tools

Execute · Critical run_with_credential This tool runs arbitrary shell commands (Execute category), which is the most severe applicable risk. Execute · High browser_login This tool executes a browser session and performs a login operation against an external site using stored credentials. Execute · High use_credential The tool executes outbound HTTP requests authenticated with stored credentials. Write · High capture_stripe_credentials This tool captures (stores/writes) Stripe API credentials into the psamvault vault.

4 of Psamvault'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 Psamvault

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

Rate limit write operations

{
  "capture_stripe_credentials": {
    "limits": [
      {
        "counter": "capture_stripe_credentials_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "check_credential_exists": {
    "limits": [
      {
        "counter": "check_credential_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 Psamvault — 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 PSAMVAULT →

Instant setup, no code required.

FULL CATALOGUE

All 11 Psamvault tools

EXECUTE 3 tools

Execute browser_login [🔐 Site Authentication] Open a visible browser and securely log into a site using a stored psamvault credenti Execute run_with_credential [🔑 API Key Operations] Run an arbitrary shell command with a credential injected as an Execute use_credential [🔑 API Key Operations] Make an authenticated HTTP request using a credential stored in psamvault.

WRITE 1 tools

Write capture_stripe_credentials [🔑 API Key Operations] Capture credentials provisioned by Stripe Projects into psamvault.

READ 7 tools

Read check_credential_exists [🔐 Site Authentication] Check whether a credential is stored for a given site. Read get_username_for_site [🔐 Site Authentication] Return the username (not the password) stored for a site. Read get_version [🛠 Entry & Orientation] Return the installed psamvault-mcp version. No session or login required. Read list_api_keys [🔑 API Key Operations] List all stored API key names with service hints. Read list_vault_sites [🔐 Site Authentication] List all sites stored in the psamvault vault. Read scan_and_protect [🔑 API Key Operations] Scan a project directory for exposed secrets in .env files and protect them. Read search_vault_tools [🛠 Entry & Orientation] Discover available psamvault tools.

EXPLORE

Related servers

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

FAQ

Questions about Psamvault

How do I prevent bulk modifications through Psamvault? +

The Psamvault server has 1 write tools including capture_stripe_credentials. 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 Psamvault.

How many tools does the Psamvault MCP server expose? +

11 tools across 3 categories: Execute, Read, Write. 7 are read-only. 4 can modify, create, or delete data.

How do I enforce a policy on Psamvault? +

Register the Psamvault 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 Psamvault tool call.

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

ENFORCE POLICY ON PSAMVAULT →

Instant setup, no code required.

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