Skip to main content
Glama
jowhee327

aws-security-mcp

by jowhee327
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

scan_inspector_findings

Scan Inspector security findings across AWS regions or Huawei Cloud providers to identify vulnerabilities. Read-only operation, modifies no resources.

Instructions

Run Inspector Findings security scanner only. Read-only. Does not modify any AWS resources.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
regionNoAWS region to scan (default: server region)
providerNoCloud provider to scan (default: aws). With huaweicloud, `region` is a Huawei Cloud region ID (e.g. cn-north-4); omit it or pass "all" to scan every region project of the account. Huawei Cloud Phase 1 is single-account (org_mode falls back to the current account with a warning).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.9.0
    • addedInput schema / properties / provider
      Added value: +{
+  "description": "Cloud provider to scan (default: aws). With huaweicloud, `region` is a Huawei Cloud region ID (e.g. cn-north-4); omit it or pass \"all\" to scan every region project of the account. Huawei Cloud Phase 1 is single-account (org_mode falls back to the current account with a warning).",
+  "enum": [
+    "aws",
+    "huaweicloud"
+  ],
+  "type": "string"
+}
  2. First observedv0.7.6

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are present, so the description carries the burden of behavioral disclosure. It does state 'Read-only. Does not modify any AWS resources,' which is an important safety trait for a scanner. However, it does not mention required permissions, return/output behavior, or any other operational side effects beyond non-modification.

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?

Two short sentences with no filler, front-loading the key 'only' scope and then adding the read-only safety note. Every sentence earns its place.

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

Completeness3/5

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

For a two-optional-parameter, read-only scanner, the description covers the core operation and safety profile, and the schema covers parameters. Still, with no output schema and no annotation enrichment, the description does not indicate what the caller should expect back after running the scan, leaving a clear but minor completeness gap.

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?

The input schema already documents both parameters with 100% coverage, including a detailed description of the provider enum and Huawei Cloud behavior. The description adds no parameter-level information, so the schema-based baseline of 3 is appropriate.

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?

The description states the tool's job with a specific verb and resource: 'Run Inspector Findings security scanner only.' The 'only' phrasing clarifies that this is not a general scanner, though it does not explicitly name sibling tools such as scan_security_hub_findings. It is clear enough to identify the tool's purpose at a glance.

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 description conveys the usage context: run only the Inspector Findings scanner, and it is read-only, so an agent can infer when it applies. It does not explicitly state when not to use it or name alternatives among the many scanner siblings, leaving some routing to inference.

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

Deploy Server

Other Tools