Aws Cdk MCP Server
aws-cdk
npm
v2.1133.0
Official
Published by AWS — an official vendor package. A brand name in a package name proves nothing; this one is verified by npm scope ownership or publish provenance.
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 6.3 = 94. What the published surface and source actually contain:
| Points | What was found | Category |
|---|---|---|
| −6.3 | Untrusted input concatenated into a command sink MTC-SRC-009 | injection |
2. Client adoption risk — 94 − 6 = 88. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −6 | capability blast radius (high) — client exposure if the model is manipulated |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
Findings 9
high Shell/command execution in server code (lib/cli/cli.js)MTC-SRC-002
In the server's implementation (`lib/cli/cli.js:77`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: agent"); async function exec(args, synthesizer) { // This is the very first code that runs, but libraries have been
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server lib/cli/cli.js
high Shell/command execution in server code (lib/cli/telemetry/library-version.js)MTC-SRC-002
In the server's implementation (`lib/cli/telemetry/library-version.js:37`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: etLibraryVersion; const child_process_1 = require("child_process"); const path = __importStar(require("path")); const ut
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server lib/cli/telemetry/library-version.js
high Shell/command execution in server code (lib/cli/util/npm.js)MTC-SRC-002
In the server's implementation (`lib/cli/util/npm.js:4`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: ew = execNpmView; const child_process_1 = require("child_process"); const util_1 = require("util"); const toolkit_lib_1
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server lib/cli/util/npm.js
high Shell/command execution in server code (lib/commands/docs.js)MTC-SRC-002
In the server's implementation (`lib/commands/docs.js:41`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: = __importStar(require("child_process")); const node_util_1 = require("node:util"); const chalk_1 = __importDefault(requ
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server lib/commands/docs.js
high Shell/command execution in server code (lib/commands/init/init.js)MTC-SRC-002
In the server's implementation (`lib/commands/init/init.js:46`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: = __importStar(require("child_process")); const path = __importStar(require("path")); const toolkit_lib_1 = require("@aw
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server lib/commands/init/init.js
high Shell/command execution in server code (lib/commands/init/os.js)MTC-SRC-002
In the server's implementation (`lib/commands/init/os.js:40`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: ts.shell = shell; const child_process = __importStar(require("child_process")); const toolkit_lib_1 = require("@aws-cdk/
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server lib/commands/init/os.js
high Shell/command execution in server code (lib/cxapp/exec.js)MTC-SRC-002
In the server's implementation (`lib/cxapp/exec.js:70`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: (build) { await exec(build); } let app = config.settings.get(['app']); if (!app) { throw new
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server lib/cxapp/exec.js
medium Untrusted input concatenated into a command sink (lib/cli/util/npm.js)MTC-SRC-009
In the server's implementation (`lib/cli/util/npm.js:14`): A shell/process command assembled from concatenated or interpolated values is command injection when any part is attacker-influenced — the OWASP canonical RCE flow. Verify what reaches the interpolated value. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: t: 3000 }), exec(`npm view aws-cdk@${currentVersion} name version deprecated --json`, { timeout: 3000 }),
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server lib/cli/util/npm.js
medium Dynamic module load from a non-literal (lib/cli/cdk-toolkit.js)MTC-SRC-005
In the server's implementation (`lib/cli/cdk-toolkit.js:670`): Loading a module chosen at runtime (from a variable) can pull in and run attacker-influenced code paths. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: }); } async import(options) { const stacks = await this.selectStacksForDeploy(options.selector, true
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server lib/cli/cdk-toolkit.js
What this scan could not see
- No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
Versions 2
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v2.1133.0 latest |
B 88/100 | 9 | 1.9.0 | 2026-07-23 |
v2.1132.1 |
B 88/100 | 9 | 1.8.0 | 2026-07-23 |
Embed this score
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
Verify this score yourself
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan aws-cdk --onlineMore in Developer Tools
Security scan results for the 1stay MCP server.
Security scan results for the Adguard Home MCP server.
Security scan results for the Ado Browser MCP server.
Security scan results for the Adobe Experience Dev MCP server.
Security scan results for the Aemet MCP server.
Security scan results for the Affinity Mcp Bridge MCP server.