Database Designer

Security checks across malware telemetry and agentic risk

Overview

This skill is a coherent database design toolkit that analyzes user-provided schema files and generates SQL recommendations, but generated migration SQL must be reviewed before use.

Install only if you want a local database schema analysis and migration-planning tool. Treat all generated migration and rollback SQL as a proposal: test it on staging or a copy, take backups first, and manually review any DROP, ALTER, constraint, or rollback step before applying it to important data.

SkillSpector

By NVIDIA
Vulnerability Patterns
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • MCP Least PrivilegeUnderdeclared Capability, Wildcard Permission, Missing Permission Declaration
  • MCP Tool PoisoningHidden Instructions, Unicode Deception, Parameter Description Injection
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
Findings (6)

Lp3

Medium
Category
MCP Least Privilege
Confidence
82% confidence
Finding
The skill appears to have effective file read/write capabilities despite not declaring any permissions, which creates a transparency and policy-enforcement gap. In an agent environment, undeclared I/O access can lead to unintended reading of sensitive files or writing migration artifacts without explicit user awareness or approval.

Tp4

High
Category
MCP Tool Poisoning
Confidence
89% confidence
Finding
The skill is presented as a broad 'database designer,' but its described behavior includes operationally sensitive capabilities such as generating migration plans, rollback SQL, and schema-modifying scripts. This mismatch can cause users or policy systems to underestimate the skill's ability to produce change-enabling artifacts that may directly affect production databases or infrastructure workflows.

Intent-Code Divergence

Medium
Confidence
98% confidence
Finding
The tool advertises rollback support for all changes, but dropped-table rollback is explicitly left as a placeholder. In a migration system, operators may rely on that promise during incident response and discover too late that destructive changes cannot be reversed, increasing outage duration and permanent data-loss risk.

Intent-Code Divergence

Medium
Confidence
96% confidence
Finding
The code claims zero-downtime migrations, but its zero-downtime column-modification path drops the original column as part of the flow. Dropping a live column can break running application versions, invalidate queries, and cause data loss or service interruption, which directly contradicts a safe expand-contract strategy.

Missing User Warnings

Medium
Confidence
86% confidence
Finding
The migration section advertises automated schema evolution and data migration capabilities without clearly warning that generated actions may alter schemas, transform data, or contribute to destructive changes if applied incorrectly. In practice, users may treat generated SQL as safe by default and execute it against important environments without sufficient review, testing, or backup controls.

Missing User Warnings

Medium
Confidence
97% confidence
Finding
The generator emits destructive SQL for dropping columns and tables without requiring explicit acknowledgment, safety flags, backup verification, or dry-run confirmation. In the context of a database-design skill, this is especially dangerous because users are likely to execute generated migration output directly, making accidental irreversible data loss much more likely.

VirusTotal

66/66 vendors flagged this skill as clean.

View on VirusTotal