AI agents invoke run_checkov to trigger actions in Amazon Location Service 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.
Checkov is an executable that performs security scanning and can generate reports or trigger downstream actions based on findings. This falls into Execute category because it runs an external operation/tool whose side effects and output depend on arguments (the infrastructure/code being scanned). It is not Destructive or Write because Checkov itself does not modify or delete data—it only analyzes and reports.
From the tool's definition Tool name 'run_checkov' indicates execution of Checkov, a static code analysis and infrastructure-as-code scanning tool.
Documented attack patterns abuse exactly the kind of access run_checkov gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Amazon Location Service MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for run_checkov:
{
"version": "1",
"default": "deny",
"tools": {
"run_checkov": {
"limits": [
{
"counter": "run_checkov_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}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.
Free to start. No card required.
run_checkov. It is categorised as a Execute tool in the Amazon Location Service MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Amazon Location Service MCP Server 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 Amazon Location Service MCP Server. Nothing to install.
run_checkov is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
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.
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.
run_checkov is provided by the Amazon Location Service MCP Server MCP server (awslabs.aws-location-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Amazon Location Service MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
805 Amazon Location Service MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.