Back to skill

Security audit

unisound-drg-grouping

Security checks for vulnerabilities and agentic risk

Overview

This medical DRG helper is mostly coherent, but its configurable API endpoint could expose sensitive case text and the API key if misused.

Install only if you are comfortable sending DRG case text to the configured medical model endpoint. Use the documented default or another approved HTTPS endpoint, de-identify real patient data first, protect the appkey, and store --output files only where medical data is allowed to reside.

Vulnerability Patterns
  • Insecure Skill Coding PracticesFinds exploitable flaws such as hardcoded secrets or command injection
  • 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
Findings (1)

T09 · Insecure Skill Coding Practices

Error
Location
scripts/run.py:81
Finding

Unrestricted API Endpoint Allows Credential and Medical Data Exfiltration

Content
View full analysis
Remediation
View remediation
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • MCP Least PrivilegeUnderdeclared Capability, Wildcard Permission, Missing Permission Declaration
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (3)

Undeclared Tool Scope

Medium
Category
MCP Least Privilege
Confidence
87% confidence
Finding

The skill manifest declares no explicit tool scope or permissions, yet the package description and detected capabilities indicate it can read files, write output files, and make network requests to an external model API. Without an allowlist in the manifest, a caller cannot easily constrain or audit those capabilities, increasing the risk of unintended data access or exfiltration when handling sensitive medical text.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

This skill sends raw user-supplied discharge summaries and related DRG question content to an external HTTPS API, and the data is likely to contain highly sensitive medical information. Even if the endpoint is described as an internal medical model, the script provides no minimization, consent prompt, masking, or transmission disclosure, so operators can unintentionally exfiltrate protected health information to a remote service.

Content

No source excerpt is available for this finding.

Missing User Warnings

Low
Category
Not specified by scanner
Confidence
89% confidence
Finding

The script persists both the original question text and model answer to an output file, which can store sensitive discharge content on disk in plaintext. In a medical workflow this creates additional confidentiality and retention risk, especially if output paths point to shared directories, logs, or long-lived artifacts without any warning or access controls.

Content

No source excerpt is available for this finding.