aws-mcp-setup

The skill is SUSPICIOUS overall due to inconsistent security posture relative to its stated purpose: it prescribes (or at least implies) downloading and running an external MCP proxy binary and interacting with external MCP/documentation endpoints, while also including credential snippets in examples. This combination creates potential credential exposure, supply-chain risk, and data routing concerns that are not adequately mitigated by explicit verifications or restrictions. If used, enforce strict provenance checks (signed binaries, verifiable checksums), avoid embedding real credentials in docs, and constrain data flows to official AWS MCP endpoints with minimal external dependencies.