RunCheckovScan

RunCheckovScan

Server AWS Terraform MCP Server stv-io/aws-terraform-mcp-server
Category Execute
Risk class High
Parameters 00 required

What RunCheckovScan does on AWS Terraform MCP Server

AI agents invoke RunCheckovScan to trigger actions in AWS Terraform MCP Server. 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 RunCheckovScan needs a policy

This tool executes an external security scanning operation (Checkov) whose effects depend on the arguments provided (which files/modules to scan). It is not a simple read operation because scanning can trigger external processes and produce variable outputs based on detected issues. While the scan itself is non-destructive and informational, it qualifies as Execute because it runs an external tool/command.

From the tool's definition Tool name 'RunCheckovScan' indicates execution of Checkov security scanning. Server description states 'security scanning with Checkov' as a core feature. Checkov is a code scanning tool that analyzes infrastructure-as-code for security and compliance issues.

Questions about RunCheckovScan

What does the RunCheckovScan tool do? +

RunCheckovScan. It is categorised as a Execute tool in the AWS Terraform 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 RunCheckovScan? +

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

What risk level is RunCheckovScan? +

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

Can I rate-limit RunCheckovScan? +

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

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

RunCheckovScan is provided by the AWS Terraform MCP Server MCP server (stv-io/aws-terraform-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.