aws-ecs-monitor

Security checks across malware telemetry and agentic risk

Overview

This looks like a legitimate AWS ECS monitoring skill, but it needs Review because it uses AWS access to read production health and logs and one load-balancer check is broader than the selected services.

Install only if you are comfortable letting this skill use an AWS CLI profile to read ECS service state, ELB target health, and CloudWatch logs. Use a dedicated read-only AWS role scoped as tightly as possible to the intended region, cluster, services, target groups, and log groups; set ECS_SERVICES explicitly; and store generated health/log reports in a protected directory.

SkillSpector

By NVIDIA
Vulnerability Patterns
  • MCP Least PrivilegeUnderdeclared Capability, Wildcard Permission, Missing Permission Declaration
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (1)

Lp3

Medium
Category
MCP Least Privilege
Confidence
87% confidence
Finding
The skill declares executable capabilities and data access patterns in its documentation and metadata (`aws`, `curl`, `python3`, environment-variable configuration, and writes to local files), but it does not declare explicit permissions for those operations. This creates a trust and review gap: consumers may authorize or run the skill without realizing it can read sensitive environment configuration, invoke shell commands against AWS, and write potentially sensitive health/log data to disk.

VirusTotal

66/66 vendors flagged this skill as clean.

View on VirusTotal