aws-security-mcp

scan_network_reachability

Run read-only network reachability scans to identify exposed paths and connectivity risks without modifying cloud resources across AWS, Huawei Cloud, Alibaba Cloud, and Azure.

Instructions

Run Network Reachability security scanner only. Read-only. Does not modify any AWS resources.

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": "scan_network_reachability"
  }
}

Input Schema

Name	Required	Description	Default
`region`	No	AWS region to scan (default: server region)
`provider`	No	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). With alicloud (EXPERIMENTAL — not yet validated against a live account), region is an Alibaba Cloud region ID (e.g. cn-hangzhou); omit or "all" to scan every region; single-account only in this phase. With azure (EXPERIMENTAL — not yet validated against a live account), the China cloud (21Vianet) is the default; set AZURE_CLOUD=global for public cloud. region is an Azure subscription ID; omit or "all" to scan every visible subscription.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.10.0Nov 8, 2026

changedInput schema / properties / provider / description

Previous value: -"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)."New value: +"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). With alicloud (EXPERIMENTAL — not yet validated against a live account), region is an Alibaba Cloud region ID (e.g. cn-hangzhou); omit or \"all\" to scan every region; single-account only in this phase. With azure (EXPERIMENTAL — not yet validated against a live account), the China cloud (21Vianet) is the default; set AZURE_CLOUD=global for public cloud. region is an Azure subscription ID; omit or \"all\" to scan every visible subscription."

changedInput schema / properties / provider / enum

Previous value: -[
-  "aws",
-  "huaweicloud"
-]New value: +[
+  "aws",
+  "huaweicloud",
+  "alicloud",
+  "azure"
+]

Changed1 schema field changedv0.9.0Sep 15, 2026

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"
+}

First observedv0.7.6Jun 7, 2026

TDQS

B3.4/5.0

Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose the most important behavioral trait, that the tool is read-only ('Read-only. Does not modify any AWS resources'), which is valuable. However, it says nothing about required permissions, runtime, rate limits, or whether findings are persisted or need save_results afterward. Also, the schema allows huaweicloud, alicloud, and azure scans, while the description mentions only AWS resources, which is a mild scope inconsistency rather than a contradiction.

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?

Three short sentences, front-loaded with the action and resource so an agent can identify the tool immediately, with no wasted preamble. 'Read-only' and 'Does not modify any AWS resources' partially restate each other, a minor redundancy that keeps it from a 5.

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 scanner with no output schema, the description covers the safety profile but omits what the scan returns, whether results persist, and that the scan may target non-AWS providers per the schema. It is adequate but leaves real gaps for an agent deciding between this and the aggregate scan tools.

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 provider and region parameters are documented in unusually rich detail in the schema, including provider-specific region semantics and experimental caveats. The description adds no parameter meaning beyond that, so the baseline 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?

The first sentence names a specific scanner ('Network Reachability security scanner') and a specific action ('Run'), which separates it from the many other scan_* siblings. The word 'only' signals that it performs the scan alone, not the reporting or orchestration that siblings like scan_and_report perform. It does not name a sibling explicitly, so it falls just short of a 5.

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?

'only' implies that this tool is for running the scanner alone, which helps distinguish it from scan_all and scan_and_report, but the description never states when to choose this tool over those alternatives, nor does it state prerequisites such as credentials or scan scope. Usage must be inferred from the name and the word 'only'.

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

Deploy Server