// MCP TOOL REFERENCE

run_checkov

Part of the AWS Cloud Control API (CCAPI) MCP Server MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

awslabs.ccapi-mcp-server Execute

// WHEN AI AGENTS USE THIS TOOL

AI agents invoke run_checkov to trigger processes or run actions in AWS Cloud Control API (CCAPI) MCP Server. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.

// WHY ENFORCE A POLICY ON RUN_CHECKOV

run_checkov can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.

// RECOMMENDED POLICY

Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.

aws-cloud-control-api-ccapi-mcp-server.yaml

tools:
  run_checkov:
    rules:
      - action: allow
        rate_limit:
          max: 10
          window: 60
        validate:
          required_args: true

See the full AWS Cloud Control API (CCAPI) MCP Server policy for all 14 tools.

// DETAILS

Tool Name run_checkov

Category Execute

MCP Server AWS Cloud Control API (CCAPI) MCP Server MCP Server

Risk Level High

// MORE AWS CLOUD CONTROL API (CCAPI) MCP SERVER TOOLS

Destructive delete_resource Destructive explain Write create_resource Write create_template Write generate_infrastructure_code Write update_resource Read check_environment_variables Read get_aws_account_info

View all 14 tools →

// WHAT CAN GO WRONG

Agents calling execute-class tools like run_checkov have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

// OTHER EXECUTE TOOLS ACROSS MCP SERVERS

Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

Atv build_stake_tx Atv build_unstake_tx Acdp start_local Pentagonal pentagonal_audit Pentagonal pentagonal_compile ACR — Agent Composition Records orient_me

// IN CONTEXT OF HIGH RISK

run_checkov is one of the high-risk operations in AWS Cloud Control API (CCAPI) MCP Server. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.

// RELATED READING

// FAQ

What does the run_checkov tool do? +

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). It is categorised as a Execute tool in the AWS Cloud Control API (CCAPI) MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on run_checkov? +

Add a rule in your Intercept YAML policy under the tools section for run_checkov. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the AWS Cloud Control API (CCAPI) MCP Server MCP server.

What risk level is run_checkov? +

run_checkov is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit run_checkov? +

Yes. Add a rate_limit block to the run_checkov 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.

How do I block run_checkov completely? +

Set action: deny in the Intercept policy for run_checkov. 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.

What MCP server provides run_checkov? +

run_checkov is provided by the AWS Cloud Control API (CCAPI) MCP Server MCP server (awslabs.ccapi-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

run_checkov

Let agents act without letting them run wild.