Skip to main content
Glama
jowhee327

aws-security-mcp

by jowhee327

scan_ecr_image_cve

Detect critical and high CVEs in ECR image layers that basic scans miss. Classifies findings as gap, confirmed, or reverse-gap against official results.

Instructions

Deep-scan ECR image layers for critical/high CVEs missed by ECR Basic/Inspector Enhanced scanning (unmanaged binaries, distro secdb gaps). Reports gap/confirmed/reverse-gap classification against official scan results. Read-only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
regionNoAWS region to scan (default: server region)
min_severityNoMinimum CVE severity to report (default: high)
suppressionsNoFalse-positive suppression list; suppressed findings go to a suppressed[] section
max_image_bytesNoSkip images whose compressed layers total more than this many bytes (default: 2 GB)
max_layer_bytesNoSkip images containing a layer larger than this many compressed bytes (default: 512 MB)
max_total_bytesNoCumulative cap on compressed layer bytes downloaded across the whole scan (default: 20 GB)
max_repositoriesNoMaximum number of repositories to scan; the rest are recorded in warnings (default: 50)
include_confirmedNoInclude confirmed finding detail rows in the report (default: false)
online_cve_lookupNoEnable NVD API 2.0 online lookup, cached 24h (default: false)
repository_filterNoGlob filter on ECR repository names (e.g. prod-*)
max_images_per_repoNoLatest-pushed N images per repo, plus any tag named 'latest' (default: 3)
platform_preferenceNoPlatform preference order for multi-arch manifest lists, e.g. ['linux/amd64', 'linux/arm64'] (default)
max_binary_scan_bytesNoCap on decompressed bytes stream-scanned per candidate binary (default: 64 MB)
Behavior4/5

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

Declares 'Read-only' and describes classification output, but with no annotations provided, it lacks disclosure of potential rate limits, authorization needs, or scan scope limitations beyond parameter constraints.

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 sentences front-load core purpose and classification, with 'Read-only' appended. No redundant information.

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?

Given no output schema and 13 parameters, the description explains output classification but lacks detail on return format or structure. Adequate but with gaps for a complex scanning tool.

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%, so baseline is 3. The description does not add extra meaning beyond schema details; it only provides overall context.

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?

Description clearly states verb 'deep-scan', resource 'ECR image layers', and distinguishes from standard ECR scanning by mentioning CVEs missed by Basic/Inspector Enhanced. Also explains output classification format.

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

Usage Guidelines4/5

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

Explicitly indicates use case for finding CVEs missed by standard scanning, but does not specify when not to use or provide direct alternatives among sibling tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jowhee327/aws-security-agent'

If you have feedback or need assistance with the MCP directory API, please join our Discord server