Skip to main content
Glama
jowhee327

aws-security-mcp

by jowhee327
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

scan_guardduty_findings

Scan GuardDuty findings across AWS or Huawei Cloud regions to detect security threats. Read-only operation; no AWS resources are modified.

Instructions

Run GuardDuty 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.6/5.0
Behavior4/5

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

Without any annotations, the description carries the full behavioral burden and it does disclose a key trait: the operation is read-only and does not modify AWS resources. This is essential side-effect communication for an agent deciding whether a scanner is safe to invoke. It omits other potential behavior details like runtime or API cost, but for a simple scanner, the non-destructive guarantee is the most important disclosure.

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

Conciseness4/5

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

The description is only two short sentences with the action and target front-loaded. 'Does not modify any AWS resources' is slightly redundant with 'Read-only,' but the overall text is efficient and respects the reader's attention.

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 low-complexity tool with fully documented optional parameters, the description covers scope and safety adequately. However, since there is no output schema, the description does not explain what the scanner returns or what happens when it runs, which an agent may need to anticipate. It also leaves the decision of when to select GuardDuty over sibling scanners entirely unaddressed.

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 provides 100% coverage for both optional parameters, including detailed region defaults and Huawei Cloud behavior. The description text itself adds no parameter-level semantics, so the baseline of 3 applies; no deduction is needed because the schema fully compensates.

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

Purpose5/5

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

The description states a specific verb and resource: 'Run GuardDuty Findings security scanner only.' The word 'only' explicitly limits the tool to this one scanner, distinguishing it from sibling tools such as scan_security_hub_findings or scan_inspector_findings. There is no ambiguity about the target resource.

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

Usage Guidelines2/5

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

The description gives no guidance on when to use this tool versus the many similar scan tools in the sibling list. It does not mention Security Hub, Inspector, Trusted Advisor, Access Analyzer, or other finding sources, nor does it specify any condition that would make GuardDuty the correct choice. The 'only' clause is a scope limiter, not a usage rule.

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