Low Risk

describe_log_groups

describe_log_groups

How to control describe_log_groups ↓

What describe_log_groups does on Amazon EKS MCP Server

AI agents call describe_log_groups 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 describe_log_groups needs a policy

The 'describe_' prefix is a standard AWS API convention for retrieving resource metadata and configuration without making changes. CloudWatch log groups are observability artifacts; describing them retrieves information only. While the description field is empty, the tool name itself provides strong semantic evidence of read-only behavior. Confidence is high due to the explicit 'describe_' naming pattern.

From the tool's definition Tool name 'describe_log_groups' indicates a describe/query operation on AWS CloudWatch log groups. The pattern of listing/describing resources without modification is characteristic of read-only operations.

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

How to control describe_log_groups

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

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

describe_log_groups 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 describe_log_groups

What does the describe_log_groups tool do? +

describe_log_groups. 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 describe_log_groups? +

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

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

Can I rate-limit describe_log_groups? +

Yes. Add a rate_limit block to the describe_log_groups 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 describe_log_groups completely? +

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

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