CONFIG CREATION WORKFLOW: Use this when generating vCluster configurations for users. This tool REQUIRES you to provide the YAML you created and automatically validates it before returning to the user. Returns validation result + formatted config. This ensures every config you create is validated.
AI agents use create-vcluster-config to create or update resources in Vcluster Yaml — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Vcluster Yaml environment.
This tool creates or modifies vCluster YAML configurations, which is a reversible write operation. It does not delete data (would be Destructive), execute arbitrary commands beyond validation (would be Execute), or move money (would be Financial). The severity is medium because misconfigured vClusters could impact cluster operations, but the validation step provides some safety guardrails.
From the tool's definition Tool description states it is for 'generating vCluster configurations' and 'automatically validates it before returning to the user', indicating it creates and modifies configuration data.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
CONFIG CREATION WORKFLOW: Use this when generating vCluster configurations for users. This tool REQUIRES you to provide the YAML you created and automatically validates it before returning to the user. Returns validation result + formatted config. This ensures every config you create is validated. It is categorised as a Write tool in the Vcluster Yaml MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Vcluster Yaml MCP server in PolicyLayer and add a rule for create-vcluster-config: 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 Vcluster Yaml. Nothing to install.
create-vcluster-config 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 create-vcluster-config 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 create-vcluster-config. 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.
create-vcluster-config is provided by the Vcluster Yaml MCP server (vcluster-yaml-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 →