AI agents invoke list_remove to trigger actions in Amazon EKS 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 description suggests removing items from a list, which could be a destructive write operation. However, the description is vague and does not specify what kind of list or data store is involved. In an EKS context, this could relate to modifying Kubernetes resource lists or configuration, which would be a Write operation.
From the tool's definition Tool name: 'list_remove', description: 'Remove occurrences of value from list.'
Documented attack patterns abuse exactly the kind of access list_remove 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_remove:
{
"version": "1",
"default": "deny",
"tools": {
"list_remove": {
"limits": [
{
"counter": "list_remove_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}list_remove 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.
Remove occurrences of value from list. It is categorised as a Execute tool in the Amazon EKS MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Amazon EKS MCP Server MCP server in PolicyLayer and add a rule for list_remove: 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_remove 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 list_remove 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_remove. 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_remove 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.