checkov_iac_scan

A execute tool on the Pengstrike MCP server.

SERVERPengstrike SOURCEwangqiongpeng/pengstrike-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/pengstrike-mcp/checkov-iac-scan.md

WHAT IT DOES

What checkov_iac_scan does on Pengstrike

AI agents invoke checkov_iac_scan to trigger actions in Pengstrike. 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 checkov_iac_scan is rated High

Checkov is a static analysis/scanning tool that executes against IaC files (Terraform, CloudFormation, etc.) to find misconfigurations. Running a scan is an Execute-category action. Given the security-focused server context (recon console, attack suite generation), this tool likely executes Checkov scans against target infrastructure definitions.

From the tool's definition Tool name 'checkov_iac_scan' suggests running Checkov, a static analysis tool for Infrastructure-as-Code (IaC) security scanning. Description is empty, lowering confidence.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs checkov_iac_scan safely

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

checkov_iac_scan Rate-limited

checkov_iac_scan 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": {
    "checkov_iac_scan": {
      "limits": [
        {
          "counter": "checkov_iac_scan_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 Pengstrike, apply this rule, and every checkov_iac_scan call is checked against it from then on.

FAQ

Questions about checkov_iac_scan

What does the checkov_iac_scan tool do? +

checkov_iac_scan is a execute tool on the Pengstrike MCP server. It is categorised as a Execute tool in the Pengstrike MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on checkov_iac_scan? +

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

What risk level is checkov_iac_scan? +

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

Can I rate-limit checkov_iac_scan? +

Yes. Add a rate_limit block to the checkov_iac_scan 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 checkov_iac_scan completely? +

Set action: deny in the PolicyLayer policy for checkov_iac_scan. 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 checkov_iac_scan? +

checkov_iac_scan is provided by the Pengstrike MCP server (wangqiongpeng/pengstrike-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Pengstrike, and thousands of servers like it.

This server

All 163 Pengstrike tools → High-risk tools on this server →

Across the catalogue

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 →