describe-cache-engine-versions
AI agents call describe-cache-engine-versions to retrieve information from Awslabs Valkey without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns information about cache engine versions available in AWS ElastiCache/MemoryDB. It has no side effects, does not modify data, and poses minimal security risk as it only exposes descriptive metadata. The empty description slightly reduces confidence, but the tool name itself is sufficiently clear to indicate a read-only operation.
From the tool's definition Tool name 'describe-cache-engine-versions' uses the verb 'describe', which is a read-only query operation. It retrieves metadata about available ElastiCache engine versions without modifying state.
Attacks that exploit this kind of access
describe-cache-engine-versions. It is categorised as a Read tool in the Awslabs Valkey MCP Server, which means it retrieves data without modifying state.
Register the Awslabs Valkey MCP server in PolicyLayer and add a rule for describe-cache-engine-versions: 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 Awslabs Valkey. Nothing to install.
describe-cache-engine-versions 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-engine-versions 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-engine-versions. 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-engine-versions is provided by the Awslabs Valkey MCP server (awslabs.valkey-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.