generate_deploy_manifests · K8s MCP: Risk & Policy

WHAT IT DOES

What generate_deploy_manifests does on K8s

AI agents use generate_deploy_manifests to create or update resources in K8s — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your K8s environment.

WHY IT NEEDS A POLICY

Why generate_deploy_manifests needs a policy

This tool generates Kubernetes deployment manifests, which are configuration files that define workloads. Generating manifests is a Write operation—it produces new configuration data. While the description is empty (lowering confidence slightly), the name and context strongly indicate manifest creation/generation.

From the tool's definition Tool name contains 'generate_deploy' and is positioned among Kubernetes deployment/manifest tools (apply_kustomize, apply_manifest, delete_pod). The sibling tools establish this server operates on Kubernetes workloads.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

generate_deploy_manifests Rate-limited

generate_deploy_manifests 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "generate_deploy_manifests": {
      "limits": [
        {
          "counter": "generate_deploy_manifests_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches K8s, so you can run agents against it safely.

FAQ

Questions about generate_deploy_manifests

What does the generate_deploy_manifests tool do? +

generate_deploy_manifests. It is categorised as a Write tool in the K8s MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on generate_deploy_manifests? +

Register the K8s MCP server in PolicyLayer and add a rule for generate_deploy_manifests: 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 K8s. Nothing to install.

What risk level is generate_deploy_manifests? +

generate_deploy_manifests is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit generate_deploy_manifests? +

Yes. Add a rate_limit block to the generate_deploy_manifests 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.

How do I block generate_deploy_manifests completely? +

Set action: deny in the PolicyLayer policy for generate_deploy_manifests. 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.

What MCP server provides generate_deploy_manifests? +

generate_deploy_manifests is provided by the K8s MCP server (jingyanjiang/k8s-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.