Low Risk

getCollectionStats

getCollectionStats

How to control getCollectionStats ↓

What getCollectionStats does on Amazon EKS MCP Server

AI agents call getCollectionStats 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.

Low Risk

Why getCollectionStats needs a policy

The tool appears designed to fetch or query collection statistics without modifying state. While the empty description reduces confidence slightly, the naming convention ('get*') and association with an EKS management server suggest read-only behavior typical of monitoring or status queries. No evidence of side effects, modifications, deletions, or external code execution.

From the tool's definition Tool name 'getCollectionStats' suggests retrieving statistics or metrics from a collection. The sibling tools include query and retrieval operations (aggregate, analyze_*) typical of read-only workloads on EKS.

Documented attack patterns abuse exactly the kind of access getCollectionStats gives an agent:

How to control getCollectionStats

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 getCollectionStats:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "getCollectionStats": {}
  }
}

getCollectionStats is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Amazon EKS MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about getCollectionStats

What does the getCollectionStats tool do? +

getCollectionStats. It is categorised as a Read tool in the Amazon EKS MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on getCollectionStats? +

Register the Amazon EKS MCP Server MCP server in PolicyLayer and add a rule for getCollectionStats: 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.

What risk level is getCollectionStats? +

getCollectionStats is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit getCollectionStats? +

Yes. Add a rate_limit block to the getCollectionStats 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.

How do I block getCollectionStats completely? +

Set action: deny in the PolicyLayer policy for getCollectionStats. 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.

What MCP server provides getCollectionStats? +

getCollectionStats 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.

Enforce policy on every Amazon EKS MCP Server tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.