Skills/PyPI/awslabs.ecs-mcp-server

awslabs.ecs-mcp-server@0.1.38

CAUTION· not started

Publisher claims: "AWS ECS MCP Server for automating containerization and deployment of web applications to AWS ECS" Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry PyPI (MCP server)Publisher awslabs · publishing for 592 daysInstalls 31,206Last detonated 5d ago
What would fix thisWatchDispute verdict

Coverage

Not started: dependency install failed; the server itself was not observed.
Tested
the dependency install step · every file read, file written and host contacted by what ran
Not tested
server startup · the tool list · tool behavior

What this means for the label: Caution here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.

Before you give it your token

It will ask for
no credential variables read in the code
Where it talks to
no vendor host named in the codeAlso docker.com, on.aws — not the publisher's domain; check what for before connecting.
What the honeypot saw
no credential files read · no network
What we could not test
server startup · the tool list · tool behavior

Connect it under the guard. Not started: dependency install failed; the server itself was not observed. The code names no credential variable; the guard pins the network to what the honeypot saw and logs every call.

$vet-skills run --net declared -- uvx awslabs.ecs-mcp-server

Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.

Is [email protected] safe to install?

KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-09 and scored it 77/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: References a credential file in the home directory; Access to sensitive file paths; Access to sensitive file paths. Summary: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 0 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
0.1sprocessdependency install exit 1 ·
0.1sclaimednot started: dependency install failed (exit 1); the server itself was not observed
0.1sprocessscript backend runs setup only
0.1sprocessno install scripts to re-run

Static findings

HIGH
References a credential file in the home directoryawslabs/ecs_mcp_server/utils/path_validation.py:113 · References a credential file in the home directory``~/.aws/credentials`` both expose credentials) or when it contains oneFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST03
MEDIUM
Python subprocess execution detectedawslabs/ecs_mcp_server/utils/docker.py:202 · Python subprocess execution detectedbuild_result = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
AST05
HIGH
Access to sensitive file pathsawslabs/ecs_mcp_server/utils/path_validation.py:19 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filescontexts in this server. A path such as ``~/.aws`` contains no traversalFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
Access to sensitive file pathstests/conftest.py:106 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system fileswith open(os.path.join(app_dir, ".env"), "w") as f:Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
Python subprocess execution detectedawslabs/ecs_mcp_server/utils/docker.py:178 · Python subprocess execution detectedbuild_result = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
AST05
MEDIUM
AWS access key pattern detectedtests/unit/test_security_integration.py:84 · AWS access key pattern detected — possible hardcoded or harvested key"aws_key": "AKIAIOSFODNN7EXAMPLE",Fix: Never read or enumerate credential locations; accept a documented environment variable instead.
AST03
MEDIUM
AWS access key pattern detectedtests/unit/test_security_integration.py:53 · AWS access key pattern detected — possible hardcoded or harvested keyassert "AKIAIOSFODNN7EXAMPLE" not in json.dumps(result)Fix: Never read or enumerate credential locations; accept a documented environment variable instead.
AST03
MEDIUM
AWS access key pattern detectedtests/unit/test_security_integration.py:108 · AWS access key pattern detected — possible hardcoded or harvested keyassert "AKIAIOSFODNN7EXAMPLE" not in result_jsonFix: Never read or enumerate credential locations; accept a documented environment variable instead.
AST03
HIGH
Access to sensitive file pathsawslabs/ecs_mcp_server/utils/path_validation.py:89 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files# "~/.aws" name the same directory there. os.path.normcase only folds case onFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
References a credential file in the home directorytests/unit/utils/test_path_validation.py:116 · References a credential file in the home directoryvalidate_path("~/.aws/credentials")Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST03
MEDIUM
Access to sensitive file pathstests/conftest.py:51 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system fileswith open(os.path.join(app_dir, ".env"), "w") as f:Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
AWS access key pattern detectedtests/unit/test_security_integration.py:35 · AWS access key pattern detected — possible hardcoded or harvested key"aws_key": "AKIAIOSFODNN7EXAMPLE",Fix: Never read or enumerate credential locations; accept a documented environment variable instead.
AST03
MEDIUM
Python subprocess execution detectedawslabs/ecs_mcp_server/utils/docker.py:143 · Python subprocess execution detecteddocker_login_result = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
AST05
MEDIUM
Python subprocess execution detectedtests/integ/mcp-inspector/utils/mcp_call_tool.py:70 · Python subprocess execution detectedproc = subprocess.Popen(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
AST05
MEDIUM
Access to sensitive file pathstests/conftest.py:50 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files# Create .env fileFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
Access to sensitive file pathstests/conftest.py:105 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files# Create .env fileFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsawslabs/ecs_mcp_server/utils/path_validation.py:113 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files``~/.aws/credentials`` both expose credentials) or when it contains oneFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
Python subprocess execution detectedawslabs/ecs_mcp_server/utils/docker.py:219 · Python subprocess execution detectedpush_result = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
AST05
HIGH
Access to sensitive file pathsawslabs/ecs_mcp_server/utils/path_validation.py:114 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files(``/`` and ``$HOME`` both pull ``~/.aws`` into a Docker build context).Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
Python subprocess execution detectedawslabs/ecs_mcp_server/utils/docker.py:249 · Python subprocess execution detectedverify_result = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
AST05
HIGH
Access to sensitive file pathsawslabs/ecs_mcp_server/utils/path_validation.py:112 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesA path is unusable when it is inside a sensitive directory (``~/.aws`` andFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
Access to sensitive file pathstests/conftest.py:161 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files# Create .env fileFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
AWS access key pattern detectedtests/unit/utils/test_response_sanitization.py:42 · AWS access key pattern detected — possible hardcoded or harvested key"access_key": "AKIAIOSFODNN7EXAMPLE",Fix: Never read or enumerate credential locations; accept a documented environment variable instead.
AST03
MEDIUM
Access to sensitive file pathstests/unit/utils/test_path_validation.py:155 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesvalidate_path("~/.ssh/id_rsa")Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
AWS access key pattern detectedtests/unit/utils/test_response_sanitization.py:54 · AWS access key pattern detected — possible hardcoded or harvested keyassert "AKIAIOSFODNN7EXAMPLE" not in str(sanitized)Fix: Never read or enumerate credential locations; accept a documented environment variable instead.
AST03
MEDIUM
Access to sensitive file pathstests/unit/utils/test_path_validation.py:116 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesvalidate_path("~/.aws/credentials")Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
References a credential file in the home directorytests/unit/utils/test_path_validation.py:155 · References a credential file in the home directoryvalidate_path("~/.ssh/id_rsa")Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST03
MEDIUM
AWS access key pattern detectedtests/unit/utils/test_response_sanitization.py:14 · AWS access key pattern detected — possible hardcoded or harvested keytext = "My access key is AKIAIOSFODNN7EXAMPLE"Fix: Never read or enumerate credential locations; accept a documented environment variable instead.
AST03
MEDIUM
Access to sensitive file pathstests/unit/utils/test_path_validation.py:111 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesvalidate_path("~/.aws")Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
AWS access key pattern detectedtests/unit/utils/test_response_sanitization.py:68 · AWS access key pattern detected — possible hardcoded or harvested key"AKIAIOSFODNN7EXAMPLE",Fix: Never read or enumerate credential locations; accept a documented environment variable instead.
AST03
MEDIUM
AWS access key pattern detectedtests/unit/utils/test_response_sanitization.py:16 · AWS access key pattern detected — possible hardcoded or harvested keyassert "AKIAIOSFODNN7EXAMPLE" not in sanitizedFix: Never read or enumerate credential locations; accept a documented environment variable instead.
AST03
MEDIUM
Access to sensitive file pathstests/unit/utils/test_path_validation.py:54 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesstarted with $HOME pointing elsewhere still protects the real ~/.aws.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05

Cost to the agent

Instructions loaded
≈66 tok
1 file · 81 in bundle
Tool list per prompt
≈0 tok
0 tools · 0 per tool
Handshake
no reply
launch to tools/list, stdio
Undocumented tools
0
description under 20 chars · avg 0

Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.

Known vulnerabilities

No advisories in OSV for awslabs.ecs-mcp-server@0.1.38 as of 5d ago. This is the package itself, not its dependencies.

What would make this Verified

3 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%
  1. Unclaimed publisher≈ +8 on the totalClaim awslabs: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
  2. References a credential file in the home directory≈ +4 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
  3. Access to sensitive file paths≈ +4 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
  4. Python subprocess execution detected≈ +2 on the totalBuild commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
  5. AWS access key pattern detected≈ +2 on the totalNever read or enumerate credential locations; accept a documented environment variable instead.
Publish a new version to PyPI, then queue it here. Not your skill? Claim the handle to get verdict changes by email.Claim awslabsPropose a patch to the maintainer