Back to skill

Security audit

File Manager

Security checks for vulnerabilities and agentic risk

Overview

This appears to be a file-management skill whose destructive file operations are purpose-aligned, but the scope and examples need review before use.

Install only if you want an agent to help modify local files. Use it on a test folder first, require previews or dry runs before any move/delete/sync command, and avoid broad paths like home directories or cloud-synced roots unless you have a backup.

Vulnerability Patterns
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • MCP Least PrivilegeUnderdeclared Capability, Wildcard Permission, Missing Permission Declaration
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Findings (3)

Lp3

Medium
Category
MCP Least Privilege
Confidence
91% confidence
Finding
The skill advertises and demonstrates file-writing and destructive file-management operations such as organize, rename, delete, move, and sync, but no explicit permissions are declared. In an agent ecosystem, missing permission declarations can bypass expected trust boundaries and cause the skill to be invoked for filesystem modifications without clear user or platform-level authorization controls.

Vague Triggers

Medium
Confidence
84% confidence
Finding
The description is broadly scoped to common file tasks like organizing files, renaming, cleanup, syncing, and automating file workflows, which could cause the skill to activate for many ordinary requests. Because the skill performs write-capable and potentially destructive filesystem actions, over-broad activation increases the chance of unintended invocation and accidental data modification.

Missing User Warnings

Medium
Confidence
88% confidence
Finding
The document provides automation commands that use flags such as --mirror, --move, and --execute, which can immediately alter or delete files if copied verbatim. In a file-management skill, these examples are especially risky because users are likely to run them directly during operational tasks, and the markdown does not prominently warn about destructive side effects or recommend a dry-run first.

Static analysis

No suspicious patterns detected.