AI agents call list_canaries to retrieve information from Amazon EKS MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'list_canaries' function retrieves canary monitoring data without modifying any resources. Canaries in EKS are typically synthetic monitors or health checks. Listing them has no side effects and only exposes existing configuration/status. Despite empty description (lowering confidence slightly), the verb 'list' is a clear indicator of read-only data retrieval.
From the tool's definition Tool name 'list_canaries' indicates a retrieval operation. The pattern of listing monitoring constructs (canaries) in EKS context follows typical read-only inventory operations.
Documented attack patterns abuse exactly the kind of access list_canaries gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Amazon EKS MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for list_canaries:
{
"version": "1",
"default": "deny",
"tools": {
"list_canaries": {}
}
} list_canaries is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
list_canaries. It is categorised as a Read tool in the Amazon EKS MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Amazon EKS MCP Server MCP server in PolicyLayer and add a rule for list_canaries: 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 EKS MCP Server. Nothing to install.
list_canaries is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_canaries 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 list_canaries. 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.
list_canaries is provided by the Amazon EKS MCP Server MCP server (awslabs.eks-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Amazon EKS 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 Amazon EKS MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.