Update the image of a deployment
AI agents use set-image 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 is a Write operation because it modifies deployment state reversibly—the image can be changed again to a different version or rolled back. However, it carries high severity because updating deployment images in a Kubernetes cluster can cause service disruption, introduce breaking changes, or deploy untested code if misused by an AI agent. The blast radius extends to all pods managed by the affected deployment.
From the tool's definition Tool name 'set-image' and description 'Update the image of a deployment' indicate modification of deployment configuration. This updates container images in running deployments, changing application code/versions in production.
Attacks that exploit this kind of access
Update the image of a deployment. 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 set-image: 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.
set-image 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 set-image 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 set-image. 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.
set-image is provided by the Kubernetes MCP Server MCP server (thekaranpargaie/kube-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 →