CheckContainerAvailability
AI agents call CheckContainerAvailability as a supporting operation in AWS Lambda Tool MCP Server workflows.
With no description available, classification relies solely on the name. 'CheckContainerAvailability' implies a read-only availability check with no obvious side effects, but confidence is low due to lack of description.
From the tool's definition Tool description is empty and uninformative; tool name 'CheckContainerAvailability' suggests a read/query operation checking availability status.
Documented attack patterns abuse exactly the kind of access CheckContainerAvailability gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and AWS Lambda Tool MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for CheckContainerAvailability:
{
"version": "1",
"default": "deny",
"tools": {
"CheckContainerAvailability": {
"limits": [
{
"counter": "checkcontaineravailability_rate",
"window": "minute",
"max": 60,
"scope": "grant"
}
]
}
}
} CheckContainerAvailability gets a rate cap, and everything else on the server is denied unless you say otherwise.
Free to start. No card required.
CheckContainerAvailability. It is categorised as a Other tool in the AWS Lambda Tool MCP Server MCP Server, which means it performs auxiliary operations.
Register the AWS Lambda Tool MCP Server 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 AWS Lambda Tool MCP Server. Nothing to install.
CheckContainerAvailability is a Other 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 AWS Lambda Tool MCP Server MCP server (awslabs.lambda-tool-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from AWS Lambda Tool 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 AWS Lambda Tool MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.