Low Risk

describe-log-streams

describe-log-streams

How to control describe-log-streams ↓

What describe-log-streams does on Amazon EKS MCP Server

AI agents call describe-log-streams 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-streams needs a policy

This tool retrieves information about log streams—a read-only operation with no side effects. While the description is empty, the semantic naming convention in AWS CloudWatch APIs (describe-* operations) strongly indicates a data retrieval function. The blast radius is minimal as it only exposes log metadata without modifying infrastructure or accessing sensitive log contents directly.

From the tool's definition Tool name 'describe-log-streams' indicates a read operation that retrieves log stream metadata from AWS EKS/CloudWatch Logs. The verb 'describe' is a standard AWS API pattern for querying/listing resource information without modification.

Documented attack patterns abuse exactly the kind of access describe-log-streams gives an agent:

How to control describe-log-streams

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "describe-log-streams": {}
  }
}

describe-log-streams 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-streams

What does the describe-log-streams tool do? +

describe-log-streams. 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-streams? +

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

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

Can I rate-limit describe-log-streams? +

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

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

describe-log-streams 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.