Validate CloudFormation template against security and compliance rules using cfn-guard. This tool performs compliance validation for CloudFormation templates. It validates: - Security best practices and controls - AWS Control Tower proactive controls - Organizational policy requirements - Resour...
Bulk/mass operation — affects multiple targets
Part of the AWS Infrastructure as Code MCP Server MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call check_cloudformation_template_compliance to retrieve information from AWS Infrastructure as Code MCP Server without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though check_cloudformation_template_compliance only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
tools:
check_cloudformation_template_compliance:
rules:
- action: allowSee the full AWS Infrastructure as Code MCP Server policy for all 8 tools.
Agents calling read-class tools like check_cloudformation_template_compliance have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.
Validate CloudFormation template against security and compliance rules using cfn-guard. This tool performs compliance validation for CloudFormation templates. It validates: - Security best practices and controls - AWS Control Tower proactive controls - Organizational policy requirements - Resource configuration compliance Use this tool to: - Validate templates against security and compliance rules - Catch policy violations before deployment - Get remediation guidance for each violation - Ensure templates meet organizational standards - Receive specific CloudFormation template fixes for each violation Returns validation results including: - is_compliant (Boolean indicating if template passes all rules) - violation_count (Number of compliance violations) - violations (List of violations categorized by severity) NOTE: Some rules check multiple sub-properties, so the violation count may appear high. Each missing or misconfigured sub-property is counted as a separate violation. OUTPUT FORMATTING REQUIREMENTS: - Start with: "Your template has X violations" - Group related violations (e.g., all PublicAccessBlock settings together) - Prioritize by severity: critical security issues first, then optional features - For repeated sub-properties, show once: "Settings (A, B, C, D) must all be true" - Add context for optional features (ObjectLock, Replication may not be needed) - Show only the properties that need to be added/changed, not entire resources - Use inline YAML comments to explain why each property is needed - Avoid redundant "Key Changes" sections - the code should be self-explanatory MANDATORY REMEDIATION REQUIREMENTS: - Provide specific CloudFormation template code fixes - Show exact YAML/JSON properties to add or modify - Use inline comments to explain each fix - Focus on what changed, not the entire resource definition Args: template_content: CloudFormation template as YAML or JSON string rules_file_path: Path to guard rules file (default: default_guard_rules.guard). It is categorised as a Read tool in the AWS Infrastructure as Code MCP Server MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for check_cloudformation_template_compliance. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the AWS Infrastructure as Code MCP Server MCP server.
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 Intercept 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 Intercept 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 AWS Infrastructure as Code MCP Server MCP server (awslabs.aws-iac-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.