AWS Cloud Control API
Direct resource management with security scanning.
10K+
14 Tools
Packaged by
Requires Secrets
Add to Docker Desktop
Version 4.43 or later needs to be installed to add the server automatically
Tools
| Name | Description |
|---|---|
explain | MANDATORY: Explain any data in clear, human-readable format. For infrastructure operations (create/update/delete): - CONSUMES generated_code_token and returns explained_token - You MUST immediately display the returned explanation to user - You MUST use the returned explained_token for create/update/delete operations For general data explanation: - Pass any data in 'content' parameter - Provides comprehensive explanation of the data structure CRITICAL: You MUST immediately display the full explanation content to the user after calling this tool. The response contains an 'explanation' field that you MUST show to the user - this is MANDATORY. Never proceed with create/update/delete operations without first showing the user what will happen. Returns: explanation: Comprehensive explanation you MUST display to user explained_token: New token for infrastructure operations (if applicable) |
run_checkov | Run Checkov security and compliance scanner on server-stored CloudFormation template. SECURITY: This tool only scans CloudFormation templates stored server-side from generate_infrastructure_code(). AI agents cannot provide different content to bypass security scanning. CRITICAL WORKFLOW REQUIREMENTS: ALWAYS after running this tool: 1. Call explain() to show the security scan results to the user (both passed and failed checks) If scan_status='FAILED' (security issues found): 2. Ask the user how they want to proceed: "fix", "proceed anyway", or "cancel" 3. WAIT for the user's actual response - do not assume their decision 4. Only after receiving user input, call approve_security_findings() with their decision If scan_status='PASSED' (all checks passed): 2. You can proceed directly to create_resource() after showing the results WORKFLOW REQUIREMENTS: 1. ALWAYS provide a concise summary of security findings (passed/failed checks) 2. Only show detailed output if user specifically requests it 3. If CRITICAL security issues found: BLOCK resource creation, explain risks, provide resolution steps, ask multiple times for confirmation with warnings 4. If non-critical security issues found: Ask user how to proceed (fix issues, proceed anyway, or cancel) |