Add or update annotations on a resource
AI agents use annotate 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.
Annotations in Kubernetes are metadata labels that can be added, updated, or removed without destructive consequences. This is a reversible modification operation (Write category). Severity is medium because malicious annotation changes could disrupt cluster monitoring, tooling integration, or governance labels, but the changes are not irreversible and do not directly execute code or cause data loss. Confidence is 0.
From the tool's definition Tool description states 'Add or update annotations on a resource' — this modifies resource metadata reversibly without deleting or executing external operations.
Attacks that exploit this kind of access
Add or update annotations on a resource. 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 annotate: 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.
annotate 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 annotate 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 annotate. 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.
annotate 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 →