run_checkov · Awslabs Valkey MCP: Risk & Policy

WHAT IT DOES

What run_checkov does on Awslabs Valkey

AI agents invoke run_checkov to trigger actions in Awslabs Valkey. 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.

WHY IT NEEDS A POLICY

Why run_checkov needs a policy

Checkov is an infrastructure-as-code security scanner that executes analysis on code/config files. Running it requires invoking an external command/process whose behavior depends on the files and arguments provided. This falls under Execute rather than Read because it performs active scanning and generates side effects (vulnerability detection, report generation).

From the tool's definition Tool name 'run_checkov' indicates execution of the Checkov security scanning tool, which runs external code analysis operations. Description is empty, limiting confidence but not changing the core assessment.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

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.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Awslabs Valkey, so you can run agents against it safely.

FAQ

Questions about run_checkov

What does the run_checkov tool do? +

run_checkov. It is categorised as a Execute tool in the Awslabs Valkey 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 Awslabs Valkey 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 Awslabs Valkey. 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 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.