check_cloudformation_template_compliance
AI agents call check_cloudformation_template_compliance 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 tool appears to perform compliance checking or validation of CloudFormation templates, which is fundamentally a read/query operation that analyzes configuration without modifying infrastructure. No data creation, deletion, code execution, or financial impact is indicated by the name.
From the tool's definition Tool name 'check_cloudformation_template_compliance' and server context (AWS ElastiCache/MemoryDB) suggest template inspection/validation. The empty description prevents definitive classification.
Attacks that exploit this kind of access
check_cloudformation_template_compliance. 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 check_cloudformation_template_compliance: 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.
check_cloudformation_template_compliance 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 check_cloudformation_template_compliance 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 check_cloudformation_template_compliance. 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.
check_cloudformation_template_compliance 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.