AI agents call describe-cache-clusters to retrieve information from Amazon Redshift MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The describe-* pattern in AWS APIs consistently retrieves resource configuration and state information without side effects. Even though the description is empty, the naming convention strongly indicates this is a read operation querying cache cluster details. Low severity because describe operations pose minimal risk—they retrieve existing data with no capability to modify, delete, or execute operations.
From the tool's definition Tool name 'describe-cache-clusters' uses the 'describe' verb, which is a standard AWS API pattern for retrieving information about resources without modification. The '-clusters' suffix indicates it queries cluster metadata.
Documented attack patterns abuse exactly the kind of access describe-cache-clusters gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Amazon Redshift MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for describe-cache-clusters:
{
"version": "1",
"default": "deny",
"tools": {
"describe-cache-clusters": {}
}
}describe-cache-clusters 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.
describe-cache-clusters. It is categorised as a Read tool in the Amazon Redshift MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Amazon Redshift MCP Server MCP server in PolicyLayer and add a rule for describe-cache-clusters: 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 Redshift MCP Server. Nothing to install.
describe-cache-clusters 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 describe-cache-clusters 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 describe-cache-clusters. 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.
describe-cache-clusters is provided by the Amazon Redshift MCP Server MCP server (awslabs.redshift-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Amazon Redshift 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 Redshift MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.