CheckContainerAvailability
AI agents call CheckContainerAvailability 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.
The name pattern 'Check[Resource]' typically indicates a query or status check operation with no side effects. However, confidence is reduced due to the empty description and lack of explicit confirmation that this is purely informational. In the ElastiCache/MemoryDB context, checking container availability would retrieve cluster or node status without modifying any data.
From the tool's definition Tool name 'CheckContainerAvailability' suggests querying or checking the status of a container (likely an ElastiCache/MemoryDB cluster or node), which is a read-only operation. No description provided to confirm intent.
Attacks that exploit this kind of access
CheckContainerAvailability. 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 CheckContainerAvailability: 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.
CheckContainerAvailability 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 CheckContainerAvailability 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 CheckContainerAvailability. 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.
CheckContainerAvailability 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.