run_checks · AWS MCP Audit MCP: Risk & Policy

WHAT IT DOES

What run_checks does on AWS MCP Audit

AI agents invoke run_checks to trigger actions in AWS MCP Audit. 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_checks needs a policy

Although the server is described as 'read-only', the run_checks tool executes operational and security assessment logic against AWS infrastructure. This is an Execute classification because it triggers external operations (AWS API calls to scan resources, run security checks) whose effects depend on what checks are run and what they discover.

From the tool's definition Tool name 'run_checks' combined with server context indicating 'running security and operational checks' across AWS environments. The server description explicitly states it 'runs...checks' as a core function.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_checks Rate-limited

run_checks 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_checks": {
      "limits": [
        {
          "counter": "run_checks_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 AWS MCP Audit, so you can run agents against it safely.

FAQ

Questions about run_checks

What does the run_checks tool do? +

run_checks. It is categorised as a Execute tool in the AWS MCP Audit 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_checks? +

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

What risk level is run_checks? +

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

Can I rate-limit run_checks? +

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

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

run_checks is provided by the AWS MCP Audit MCP server (oldcoder01/aws-mcp-audit). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.