AI agents invoke manage_eks_stacks to trigger actions in AWS Lambda Tool MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
The name suggests managing EKS (Elastic Kubernetes Service) stacks, which likely involves creating, updating, or deleting Kubernetes cluster infrastructure. 'Manage' implies a broad set of operations that could span Write, Execute, or Destructive. Given the infrastructure nature of EKS stacks and the potential for irreversible changes, Execute is the most appropriate baseline category.
From the tool's definition Tool name 'manage_eks_stacks' — no description provided.
Documented attack patterns abuse exactly the kind of access manage_eks_stacks gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and AWS Lambda Tool MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for manage_eks_stacks:
{
"version": "1",
"default": "deny",
"tools": {
"manage_eks_stacks": {
"limits": [
{
"counter": "manage_eks_stacks_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}manage_eks_stacks stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
manage_eks_stacks. It is categorised as a Execute tool in the AWS Lambda Tool MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the AWS Lambda Tool MCP Server MCP server in PolicyLayer and add a rule for manage_eks_stacks: 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 AWS Lambda Tool MCP Server. Nothing to install.
manage_eks_stacks is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the manage_eks_stacks 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 manage_eks_stacks. 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.
manage_eks_stacks is provided by the AWS Lambda Tool MCP Server MCP server (awslabs.lambda-tool-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from AWS Lambda Tool MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
805 AWS Lambda Tool MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.