Create a deployment with specified update strategy
AI agents use create_deployment_with_strategy to create or update resources in Kubernetes MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Kubernetes MCP Server environment.
This tool creates (instantiates) a new Kubernetes Deployment object with a specified rolling update or canary strategy. Creation of infrastructure resources is a Write operation because it modifies cluster state reversibly—the deployment can subsequently be deleted or modified.
From the tool's definition Tool name 'create_deployment_with_strategy' and description 'Create a deployment with specified update strategy' indicate the creation of a Kubernetes deployment resource, which is a reversible modification operation.
Attacks that exploit this kind of access
Create a deployment with specified update strategy. It is categorised as a Write tool in the Kubernetes MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Kubernetes MCP Server MCP server in PolicyLayer and add a rule for create_deployment_with_strategy: 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 Kubernetes MCP Server. Nothing to install.
create_deployment_with_strategy 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_deployment_with_strategy 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_deployment_with_strategy. 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_deployment_with_strategy is provided by the Kubernetes MCP Server MCP server (surukanti/k8s-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 →