apply_k8s_manifest
Applies a Kubernetes manifest to a cluster using server-side apply. This is similar to running kubectl apply --server-side.
This record as markdown: /tools/com-googleapis-container-mcp/apply-k8s-manifest.md
What apply_k8s_manifest does on Mcp
AI agents use apply_k8s_manifest to create or update resources in Mcp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
dryRun | boolean | — | Optional. If true, run in dry-run mode. |
parent | string | Yes | Required. The cluster to apply the manifest to. Format: projects/{project}/locations/{location}/clusters/{cluster} |
yamlManifest | string | Yes | Required. The YAML manifest to apply. |
forceConflicts | boolean | — | Optional. If true, force conflicts resolution when applying. |
Parameters from the server's own tool schema.
Why apply_k8s_manifest is rated Medium
Applying a Kubernetes manifest creates or modifies resources in a cluster (deployments, services, configs, RBAC rules, etc.). This is a Write operation since `kubectl apply` is additive/updating and generally reversible, but it carries high severity because misuse could reconfigure critical cluster workloads, expose services, escalate privileges, or alter security policies across the cluster.
From the tool's definition Applies a Kubernetes manifest to a cluster using server-side apply. This is similar to running `kubectl apply --server-side`.
Attacks that exploit this kind of access
The rule that runs apply_k8s_manifest safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For apply_k8s_manifest, this is the rule to start with:
apply_k8s_manifest stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp, apply this rule, and every apply_k8s_manifest call is checked against it from then on.
Questions about apply_k8s_manifest
Applies a Kubernetes manifest to a cluster using server-side apply. This is similar to running kubectl apply --server-side. It is categorised as a Write tool in the Mcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
apply_k8s_manifest accepts 4 parameters: dryRun, parent, yamlManifest, forceConflicts. Required: parent, yamlManifest. The full parameter table on this page comes from the server's own tool schema.
Register the MCP server in PolicyLayer and add a rule for apply_k8s_manifest: 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 Mcp. Nothing to install.
apply_k8s_manifest 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 apply_k8s_manifest 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 apply_k8s_manifest. 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.
apply_k8s_manifest is provided by the MCP server (https://container.googleapis.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on , and thousands of servers like it.
This server
Across the catalogue