Medium Risk

generate_app_manifest

Generate Kubernetes manifest for a deployment and service. This tool generates Kubernetes manifests for deploying an application to an EKS cluster, creating both a Deployment and a LoadBalancer Service. The generated manifest can be applied to a cluster using the apply_yaml tool, useful for depl...

Part of the Amazon EKS MCP Server MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents use generate_app_manifest to create or modify resources in Amazon EKS MCP Server. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call generate_app_manifest repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Amazon EKS MCP Server.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

amazon-eks-mcp-server.yaml
tools:
  generate_app_manifest:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full Amazon EKS MCP Server policy for all 16 tools.

Tool Name generate_app_manifest
Category Write
Risk Level Medium

View all 16 tools →

Agents calling write-class tools like generate_app_manifest have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

What does the generate_app_manifest tool do? +

Generate Kubernetes manifest for a deployment and service. This tool generates Kubernetes manifests for deploying an application to an EKS cluster, creating both a Deployment and a LoadBalancer Service. The generated manifest can be applied to a cluster using the apply_yaml tool, useful for deploying containerized applications, creating load-balanced services, and standardizing deployment configurations. ## Requirements - The server must be run with the `--allow-write` flag ## Generated Resources - **Deployment**: Manages the application pods with specified replicas and resource requests - **Service**: LoadBalancer type service that exposes the application externally ## Usage Tips - Use 2 or more replicas for production workloads - Set appropriate resource requests based on application needs - Use internal load balancers for services that should only be accessible within the VPC - The generated manifest can be modified before applying if needed Args: ctx: MCP context app_name: Name of the application (used for deployment and service names) image_uri: Full ECR image URI with tag port: Container port that the application listens on replicas: Number of replicas to deploy cpu: CPU request for each container memory: Memory request for each container namespace: Kubernetes namespace to deploy to load_balancer_scheme: AWS load balancer scheme (internal or internet-facing) output_dir: Directory to save the manifest file Returns: GenerateAppManifestResponse: The complete Kubernetes manifest content and output file path. It is categorised as a Write tool in the Amazon EKS MCP Server 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_app_manifest? +

Add a rule in your Intercept YAML policy under the tools section for generate_app_manifest. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Amazon EKS MCP Server MCP server.

What risk level is generate_app_manifest? +

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

Can I rate-limit generate_app_manifest? +

Yes. Add a rate_limit block to the generate_app_manifest rule in your Intercept 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_app_manifest completely? +

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

What MCP server provides generate_app_manifest? +

generate_app_manifest is provided by the Amazon EKS MCP Server MCP server (awslabs.eks-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.