Apply a Kubernetes YAML from a local file. This tool applies Kubernetes resources defined in a YAML file to an EKS cluster, similar to the `kubectl apply` command. It supports multi-document YAML files and can create or update resources, useful for deploying applications, creating Kubernetes res...
Part of the Amazon EKS MCP Server MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents use apply_yaml 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 apply_yaml 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.
tools:
apply_yaml:
rules:
- action: allow
rate_limit:
max: 30
window: 60See the full Amazon EKS MCP Server policy for all 16 tools.
Agents calling write-class tools like apply_yaml have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
Apply a Kubernetes YAML from a local file. This tool applies Kubernetes resources defined in a YAML file to an EKS cluster, similar to the `kubectl apply` command. It supports multi-document YAML files and can create or update resources, useful for deploying applications, creating Kubernetes resources, and applying complete application stacks. IMPORTANT: Use this tool instead of 'kubectl apply -f' commands. ## Requirements - The server must be run with the `--allow-write` flag - The YAML file must exist and be accessible to the server - The path must be absolute (e.g., '/home/user/manifests/app.yaml') - The EKS cluster must exist and be accessible ## Response Information The response includes the number of resources created, number of resources updated (when force=True), and whether force was applied. Args: ctx: MCP context yaml_path: Absolute path to the YAML file to apply cluster_name: Name of the EKS cluster namespace: Default namespace to use for resources force: Whether to update resources if they already exist (like kubectl apply) Returns: ApplyYamlResponse with operation result. 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.
Add a rule in your Intercept YAML policy under the tools section for apply_yaml. 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.
apply_yaml 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_yaml 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.
Set action: deny in the Intercept policy for apply_yaml. 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_yaml 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.
Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.