Skip to main content
Glama
jowhee327

aws-security-mcp

by jowhee327
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

scan_dns_dangling

Detect dangling DNS records that pose subdomain takeover risks in AWS. Read-only scanner identifies vulnerable DNS entries without modifying resources.

Instructions

Run Dangling DNS 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

A4/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It explicitly states 'Read-only' and 'Does not modify any AWS resources,' which covers the most critical safety behavior. However, it does not mention return format, permission requirements, or that the provider parameter can target Huawei Cloud, which is a notable omission for a tool with cross-provider support.

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?

The description consists of three short, front-loaded sentences: the purpose, the read-only nature, and no modification guarantee. Every sentence adds distinct value with zero fluff. This is an efficient, well-structured description.

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?

For a read-only scanner with two optional parameters and no output schema, the description adequately covers the primary purpose and safety profile. It does not mention provider support in the text, but the schema fully covers that, and no output format expectations are stated. Minor gaps are the lack of return-value hints and the AWS-specific language that might confuse when provider=huaweicloud, but overall this is reasonably complete.

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 has 100% description coverage for both parameters, including detail on the provider enum and Huawei Cloud behavior. The tool description adds no additional parameter-level meaning, so the baseline score of 3 applies. The description's reference to 'AWS resources' is slightly less general than the schema's provider parameter, which supports huaweicloud as well.

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 ('Run'), a clear resource ('Dangling DNS security scanner'), and the word 'only' distinguishes it from sibling scanner tools. An agent can immediately tell this is a targeted scan for dangling DNS rather than a general scan tool. This effectively differentiates it from the many other scan_* siblings.

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 implies usage context ('Dangling DNS security scanner only') but does not explicitly state when to use this versus alternatives like scan_all or other scan_* tools. There is no mention of prerequisites, exclusions, or a preferred workflow. This leaves the agent to infer the appropriate selection from the name and sibling context.

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