Create a new encrypted credential vault with a password
AI agents use creds_create_vault to create or update resources in ML Lab MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ML Lab MCP environment.
This tool creates a new encrypted vault for storing credentials. While it is reversible (a vault can be deleted), it is a write operation that establishes a new security-sensitive resource. The severity is high because credential vaults store sensitive authentication information; misuse could lead to creation of vaults that lock out legitimate users or create security vulnerabilities.
From the tool's definition Tool name includes 'create' and description states 'Create a new encrypted credential vault with a password'. The verb 'create' indicates a write operation that produces a new persistent resource.
Attacks that exploit this kind of access
Create a new encrypted credential vault with a password. It is categorised as a Write tool in the ML Lab MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ML Lab MCP server in PolicyLayer and add a rule for creds_create_vault: 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 ML Lab MCP. Nothing to install.
creds_create_vault 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 creds_create_vault 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 creds_create_vault. 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.
creds_create_vault is provided by the ML Lab MCP server (pushpullcommitpush/ml-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 →