Store a new credential in the vault. Returns an opaque handle — you will never see the credential values.
AI agents use vault_store to create or update resources in Kova Mind MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Kova Mind MCP Server environment.
This tool creates new credential records in a secure vault. It is a Write operation (reversible via deletion), but severity is high because it handles sensitive credentials — an AI agent misusing it could store malicious or unauthorized credentials, potentially enabling privilege escalation or credential theft scenarios.
From the tool's definition 'Store a new credential in the vault' — creates a new entry; 'you will never see the credential values' confirms write-only storage of sensitive secrets.
Attacks that exploit this kind of access
Store a new credential in the vault. Returns an opaque handle — you will never see the credential values. It is categorised as a Write tool in the Kova Mind MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Kova Mind MCP Server MCP server in PolicyLayer and add a rule for vault_store: 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 Kova Mind MCP Server. Nothing to install.
vault_store 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_store 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_store. 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_store is provided by the Kova Mind MCP Server MCP server (kovamind/mcp-server). 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 →