cloud-audit-mcp

Run all checks

run_all_checks

Read-onlyIdempotent

Run all AWS security-posture checks sorted worst-first, with optional filtering to a minimum severity so you can prioritize risks.

Instructions

Runs the whole catalog, sorted worst-first, optionally filtered to a minimum severity.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "run_all_checks"
  }
}

Input Schema

Name	Required	Description	Default
`severityAtLeast`	No	Only return findings at this severity or worse. Default: everything.

Output Schema

Name	Required	Description	Default
`mode`	Yes
`findings`	Yes
`accountId`	Yes
`checksRun`	Yes
`bySeverity`	Yes
`findingCount`	Yes
`severityAtLeast`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 31, 2026

TDQS

A3.6/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds one genuine behavioral detail — results are returned 'worst-first' — but says nothing about scan scope, runtime, throttling, or whether prior results are replaced. Adequate, not rich.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One front-loaded sentence with zero filler; every clause (scope, ordering, optional filter) carries information. Nothing is padded or repeated.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists so return values need no explanation, the parameter is fully documented, and annotations cover safety and idempotency for a read-only bulk operation. What remains missing is routing guidance among the five siblings (run_check, summarize_posture, list_checks), which keeps this from a 5.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and the single parameter's semantics ('at this severity or worse. Default: everything.') are fully spelled out in the schema. The description's 'optionally filtered to a minimum severity' restates that without adding format or default information, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a concrete verb and resource ('runs the whole catalog') plus the output ordering ('sorted worst-first'), which lets an agent infer this is the bulk counterpart to run_check. It never names run_check or list_checks explicitly, so the differentiation is inferred rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'the whole catalog' implicitly signals when to pick this over the single-check sibling run_check, and 'optionally filtered' implies the filter is not required. But there is no explicit when-to-use, when-not-to-use, or named alternative, and no mention of cost/latency tradeoffs versus running individual checks.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server