Back to skill

Security audit

文档数据库管理(免费版)

Security checks for vulnerabilities and agentic risk

Overview

This is a disclosed MongoDB Atlas admin helper, but users should treat it as high-impact because it can guide real cloud management API changes.

Install only if you understand it is for cloud administration. Use least-privilege Atlas API credentials, run dry-run first, avoid --yes unless you have reviewed the requested operation, and be aware that the included documentation appears incomplete because referenced scripts are not bundled.

Vulnerability Patterns
  • Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
  • Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
  • Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
  • Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs
Vulnerability Patterns
  • 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
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (2)

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
91% confidence
Finding

The file presents the skill name, description, usage instructions, warnings, and examples exclusively in Chinese. Under the policy, forcing a specific language without user opt-in is a natural-language policy violation unless the locale constraint is explicitly justified or alternatives are offered.

Content

No source excerpt is available for this finding.

Intent-Code Divergence

Low
Category
Not specified by scanner
Confidence
92% confidence
Finding

The documentation inconsistently instructs users to set ATLAS_CLIENT_ID/ATLAS_CLIENT_SECRET earlier, but later switches to a generic API_KEY configuration. In an admin API skill that can perform real cloud management actions, this mismatch can cause misconfiguration, failed authentication, accidental use of the wrong secret, or unsafe credential handling practices.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.