CDP Tools — the complete, unedited output of the deterministic mcptrustchecker engine v1.5.0, scanned . Every finding, capability tag and score component below is exactly what the engine produced — no AI, no post-processing.
{
"tool": {
"name": "mcptrustchecker",
"version": "1.5.0",
"methodologyVersion": "mcptrustchecker-1.4"
},
"target": {
"id": "cdp-tools-mcp",
"source": {
"kind": "package",
"origin": "cdp-tools-mcp"
},
"server": {
"name": "cdp-tools-mcp"
}
},
"grade": "D",
"score": {
"score": 63,
"grade": "D",
"band": "D",
"categorySubtotals": {
"injection": 37.1,
"exfiltration": 0,
"permissions": 0,
"supply-chain": 0,
"network": 0,
"hygiene": 0
},
"vector": [
{
"ruleId": "MTC-SRC-009",
"category": "injection",
"severity": "medium",
"confidence": "strong",
"rawWeight": 9,
"confidenceMult": 0.7,
"diminishingFactor": 1,
"appliedPenalty": 6.3
},
{
"ruleId": "MTC-SRC-010",
"category": "injection",
"severity": "high",
"confidence": "strong",
"rawWeight": 22,
"confidenceMult": 0.7,
"diminishingFactor": 1,
"appliedPenalty": 15.4
},
{
"ruleId": "MTC-SRC-011",
"category": "injection",
"severity": "high",
"confidence": "strong",
"rawWeight": 22,
"confidenceMult": 0.7,
"diminishingFactor": 1,
"appliedPenalty": 15.4
}
],
"gatesFired": [],
"methodologyVersion": "mcptrustchecker-1.4"
},
"capability": {
"level": "high",
"reasons": [
"can execute shell commands or code"
],
"tags": [
"code-exec"
]
},
"coverage": {
"level": "source",
"inputs": {
"toolSurface": false,
"implementationSource": true,
"packageMetadata": true,
"liveTransport": false
},
"caveats": [
"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>\"."
]
},
"findings": [
{
"ruleId": "MTC-SRC-010",
"title": "Dynamic evaluation of a non-literal value (build/utils/modal-detector.js)",
"category": "injection",
"severity": "high",
"confidence": "strong",
"description": "In the server's implementation (`build/utils/modal-detector.js:69`): Evaluating a runtime value as code (rather than a fixed literal) executes whatever reaches it — a direct RCE primitive, and almost never necessary in legitimate code. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.",
"remediation": "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": {
"kind": "server",
"name": "build/utils/modal-detector.js"
},
"evidence": "eval(",
"owasp": "LLM05:2025 Improper Output Handling",
"data": {
"rule": "MTC-SRC-010",
"file": "build/utils/modal-detector.js",
"line": 69
}
},
{
"ruleId": "MTC-SRC-011",
"title": "Assembled command execution and dynamic evaluation in the same server",
"category": "injection",
"severity": "high",
"confidence": "strong",
"description": "The implementation builds shell commands out of runtime values AND evaluates runtime values as code. Each is a separate arbitrary-execution primitive; a server exposing both gives anything that reaches either one a direct path to running attacker-chosen code.",
"remediation": "Remove the dynamic eval, and pass command arguments as an argv array instead of building a shell string. If both are genuinely required, constrain and validate every value that can reach them.",
"location": {
"kind": "server",
"name": "implementation"
},
"owasp": "LLM05:2025 Improper Output Handling",
"data": {
"rules": [
"MTC-SRC-009",
"MTC-SRC-010"
]
}
},
{
"ruleId": "MTC-SRC-001",
"title": "Dynamic code execution in server code (build/tools/input-tools.js)",
"category": "permissions",
"severity": "high",
"confidence": "strong",
"description": "In the server's implementation (`build/tools/input-tools.js:484`): Evaluating strings as code is the most direct RCE primitive; if any tool input reaches it, the server executes attacker-chosen code. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.",
"remediation": "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": {
"kind": "server",
"name": "build/tools/input-tools.js"
},
"evidence": "eval(",
"owasp": "LLM05:2025 Improper Output Handling",
"data": {
"rule": "MTC-SRC-001",
"file": "build/tools/input-tools.js",
"line": 484
}
},
{
"ruleId": "MTC-SRC-001",
"title": "Dynamic code execution in server code (build/tools/inspection-tools.js)",
"category": "permissions",
"severity": "high",
"confidence": "strong",
"description": "In the server's implementation (`build/tools/inspection-tools.js:93`): Evaluating strings as code is the most direct RCE primitive; if any tool input reaches it, the server executes attacker-chosen code. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.",
"remediation": "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": {
"kind": "server",
"name": "build/tools/inspection-tools.js"
},
"evidence": "eval(",
"owasp": "LLM05:2025 Improper Output Handling",
"data": {
"rule": "MTC-SRC-001",
"file": "build/tools/inspection-tools.js",
"line": 93
}
},
{
"ruleId": "MTC-SRC-001",
"title": "Dynamic code execution in server code (build/utils/modal-detector.js)",
"category": "permissions",
"severity": "high",
"confidence": "strong",
"description": "In the server's implementation (`build/utils/modal-detector.js:69`): Evaluating strings as code is the most direct RCE primitive; if any tool input reaches it, the server executes attacker-chosen code. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.",
"remediation": "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": {
"kind": "server",
"name": "build/utils/modal-detector.js"
},
"evidence": "eval(",
"owasp": "LLM05:2025 Improper Output Handling",
"data": {
"rule": "MTC-SRC-001",
"file": "build/utils/modal-detector.js",
"line": 69
}
},
{
"ruleId": "MTC-SRC-002",
"title": "Shell/command execution in server code (build/chrome-launcher.js)",
"category": "permissions",
"severity": "high",
"confidence": "strong",
"description": "In the server's implementation (`build/chrome-launcher.js:5`): 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.",
"remediation": "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": {
"kind": "server",
"name": "build/chrome-launcher.js"
},
"evidence": "child_process",
"owasp": "LLM05:2025 Improper Output Handling",
"data": {
"rule": "MTC-SRC-002",
"file": "build/chrome-launcher.js",
"line": 5
}
},
{
"ruleId": "MTC-SRC-002",
"title": "Shell/command execution in server code (build/runners/docker-compose-runner.js)",
"category": "permissions",
"severity": "high",
"confidence": "strong",
"description": "In the server's implementation (`build/runners/docker-compose-runner.js:5`): 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.",
"remediation": "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": {
"kind": "server",
"name": "build/runners/docker-compose-runner.js"
},
"evidence": "child_process",
"owasp": "LLM05:2025 Improper Output Handling",
"data": {
"rule": "MTC-SRC-002",
"file": "build/runners/docker-compose-runner.js",
"line": 5
}
},
{
"ruleId": "MTC-SRC-002",
"title": "Shell/command execution in server code (build/runners/docker-runner.js)",
"category": "permissions",
"severity": "high",
"confidence": "strong",
"description": "In the server's implementation (`build/runners/docker-runner.js:5`): 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.",
"remediation": "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": {
"kind": "server",
"name": "build/runners/docker-runner.js"
},
"evidence": "child_process",
"owasp": "LLM05:2025 Improper Output Handling",
"data": {
"rule": "MTC-SRC-002",
"file": "build/runners/docker-runner.js",
"line": 5
}
},
{
"ruleId": "MTC-SRC-002",
"title": "Shell/command execution in server code (build/runners/native-runner.d.ts)",
"category": "permissions",
"severity": "high",
"confidence": "strong",
"description": "In the server's implementation (`build/runners/native-runner.d.ts:3`): 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.",
"remediation": "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": {
"kind": "server",
"name": "build/runners/native-runner.d.ts"
},
"evidence": "spawn (",
"owasp": "LLM05:2025 Improper Output Handling",
"data": {
"rule": "MTC-SRC-002",
"file": "build/runners/native-runner.d.ts",
"line": 3
}
},
{
"ruleId": "MTC-SRC-002",
"title": "Shell/command execution in server code (build/runners/native-runner.js)",
"category": "permissions",
"severity": "high",
"confidence": "strong",
"description": "In the server's implementation (`build/runners/native-runner.js:3`): 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.",
"remediation": "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": {
"kind": "server",
"name": "build/runners/native-runner.js"
},
"evidence": "spawn (",
"owasp": "LLM05:2025 Improper Output Handling",
"data": {
"rule": "MTC-SRC-002",
"file": "build/runners/native-runner.js",
"line": 3
}
},
{
"ruleId": "MTC-SRC-002",
"title": "Shell/command execution in server code (build/server-manager.js)",
"category": "permissions",
"severity": "high",
"confidence": "strong",
"description": "In the server's implementation (`build/server-manager.js:751`): 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.",
"remediation": "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": {
"kind": "server",
"name": "build/server-manager.js"
},
"evidence": "child_process",
"owasp": "LLM05:2025 Improper Output Handling",
"data": {
"rule": "MTC-SRC-002",
"file": "build/server-manager.js",
"line": 751
}
},
{
"ruleId": "MTC-SRC-002",
"title": "Shell/command execution in server code (build/supervisor/child-manager.d.ts)",
"category": "permissions",
"severity": "high",
"confidence": "strong",
"description": "In the server's implementation (`build/supervisor/child-manager.d.ts:24`): 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.",
"remediation": "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": {
"kind": "server",
"name": "build/supervisor/child-manager.d.ts"
},
"evidence": "spawn(",
"owasp": "LLM05:2025 Improper Output Handling",
"data": {
"rule": "MTC-SRC-002",
"file": "build/supervisor/child-manager.d.ts",
"line": 24
}
},
{
"ruleId": "MTC-SRC-002",
"title": "Shell/command execution in server code (build/supervisor/child-manager.js)",
"category": "permissions",
"severity": "high",
"confidence": "strong",
"description": "In the server's implementation (`build/supervisor/child-manager.js:16`): 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.",
"remediation": "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": {
"kind": "server",
"name": "build/supervisor/child-manager.js"
},
"evidence": "child_process",
"owasp": "LLM05:2025 Improper Output Handling",
"data": {
"rule": "MTC-SRC-002",
"file": "build/supervisor/child-manager.js",
"line": 16
}
},
{
"ruleId": "MTC-SRC-002",
"title": "Shell/command execution in server code (build/tools/screenshot-tools.js)",
"category": "permissions",
"severity": "high",
"confidence": "strong",
"description": "In the server's implementation (`build/tools/screenshot-tools.js:11`): 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.",
"remediation": "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": {
"kind": "server",
"name": "build/tools/screenshot-tools.js"
},
"evidence": "child_process",
"owasp": "LLM05:2025 Improper Output Handling",
"data": {
"rule": "MTC-SRC-002",
"file": "build/tools/screenshot-tools.js",
"line": 11
}
},
{
"ruleId": "MTC-SRC-009",
"title": "Untrusted input concatenated into a command sink (build/server-manager.js)",
"category": "injection",
"severity": "medium",
"confidence": "strong",
"description": "In the server's implementation (`build/server-manager.js:752`): 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.",
"remediation": "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": {
"kind": "server",
"name": "build/server-manager.js"
},
"evidence": "exec(`lsof -ti :${",
"owasp": "LLM05:2025 Improper Output Handling",
"data": {
"rule": "MTC-SRC-009",
"file": "build/server-manager.js",
"line": 752
}
},
{
"ruleId": "MTC-SRC-005",
"title": "Dynamic module load from a non-literal (build/helpers/parser-plugins.js)",
"category": "permissions",
"severity": "medium",
"confidence": "heuristic",
"description": "In the server's implementation (`build/helpers/parser-plugins.js:51`): 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.",
"remediation": "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": {
"kind": "server",
"name": "build/helpers/parser-plugins.js"
},
"evidence": "import(url)",
"owasp": "LLM05:2025 Improper Output Handling",
"data": {
"rule": "MTC-SRC-005",
"file": "build/helpers/parser-plugins.js",
"line": 51
}
}
],
"toxicFlows": [],
"capabilities": [],
"surfaceDigest": "b5f6ae17613bbe14b801f26450c83f042f6fe492bacb3663b4936855d304c245",
"stats": {
"tools": 0,
"prompts": 0,
"resources": 0,
"findingsBySeverity": {
"critical": 0,
"high": 14,
"medium": 2,
"low": 0,
"info": 0
}
}
}