vault_set
AI agents use vault_set to create or update resources in Secret Vault MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Secret Vault MCP Server environment.
vault_set writes/stores secrets into the encrypted vault, which is a reversible data modification operation. This is Write rather than Destructive (no deletion) or Execute (no code execution). Severity is high because compromised tool use could write malicious secrets or overwrite legitimate ones, affecting system security and application behavior downstream.
From the tool's definition Tool name 'vault_set' combined with server context indicating AES-256-GCM encrypted secret storage. Sibling tools include 'vault_delete', 'vault_update_tags', 'vault_import', and 'vault_rotate', establishing this as a secret management system.
Attacks that exploit this kind of access
vault_set. It is categorised as a Write tool in the Secret Vault MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Secret Vault MCP Server MCP server in PolicyLayer and add a rule for vault_set: 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 Secret Vault MCP Server. Nothing to install.
vault_set 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 vault_set 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 vault_set. 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.
vault_set is provided by the Secret Vault MCP Server MCP server (sam-ueckert/vault-mcp). 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 →