manage_eks_stacks
AI agents call manage_eks_stacks as a supporting operation in Amazon MQ MCP Server workflows.
The description is empty, so we cannot determine exactly what this tool does from its description. The name suggests managing EKS (Elastic Kubernetes Service) stacks, which could involve read, write, or destructive operations. However, 'manage' is ambiguous — it could mean listing, updating, or deleting stacks. Given the context of an AmazonMQ MCP server, this tool seems out of place, further reducing confidence.
From the tool's definition Tool name is 'manage_eks_stacks' but description is empty or uninformative
Attacks that exploit this kind of access
manage_eks_stacks. It is categorised as a Other tool in the Amazon MQ MCP Server MCP Server, which means it performs auxiliary operations.
Register the Amazon MQ 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 Amazon MQ MCP Server. Nothing to install.
manage_eks_stacks is a Other tool with low risk. Read-only tools are generally safe to allow by default.
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 Amazon MQ MCP Server MCP server (awslabs.amazon-mq-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.