run_checkov

A execute tool on the AWS MCP server.

SERVERAWS SOURCE@awslabs/mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity verified Pull the record →

This record as markdown: /tools/aws/run-checkov.md

WHAT IT DOES

What run_checkov does on AWS

AI agents invoke run_checkov to trigger actions in AWS. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

RISK

Why run_checkov is rated High

The tool invokes Checkov, which runs external security scanning operations with effects determined by supplied arguments (target paths, policies, cloud provider configs). This is Execute rather than Read because it actively processes and triggers security analysis workflows rather than simply retrieving data.

From the tool's definition Tool named 'run_checkov' on AWS server; Checkov is a static analysis and infrastructure-as-code security scanning tool that executes security checks and policy validation against cloud configurations and code.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs run_checkov safely

PolicyLayer is an MCP gateway: it sits between your AI agents and AWS, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For run_checkov, this is the rule to start with:

run_checkov Rate-limited

run_checkov stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "run_checkov": {
      "limits": [
        {
          "counter": "run_checkov_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect AWS, apply this rule, and every run_checkov call is checked against it from then on.

FAQ

Questions about run_checkov

What does the run_checkov tool do? +

run_checkov is a execute tool on the AWS MCP server. It is categorised as a Execute tool in the AWS 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? +

Register the AWS MCP server in PolicyLayer and add a rule for run_checkov: 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. Nothing to install.

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 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.

How do I block run_checkov completely? +

Set action: deny in the PolicyLayer 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 MCP server (@awslabs/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on AWS, and thousands of servers like it.

This server

All 300 AWS tools → High-risk tools on this server →

Across the catalogue

run on 0sec →shortcuts_run on Apple Apps MCP →run_emba_scan on EMBA-MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →