Tp2
- Category
- MCP Tool Poisoning
- Confidence
- 85% confidence
- Finding
Mixing characters from multiple Unicode scripts in a single identifier is a common technique to create visually ambiguous tool names.
- Content
Security audit
Security checks for vulnerabilities and agentic risk
This disk-cleanup advisor needs review because some recommendations presented as safe can permanently erase project history, logs, or stored application data.
Use read-only reports until the cleanup guidance is corrected. Never treat .git/objects/ as disposable. Review exact targets and backups before deleting files or Docker volumes, avoid blanket privileged log wipes, and expect unrelated promotional content.
Mixing characters from multiple Unicode scripts in a single identifier is a common technique to create visually ambiguous tool names.
The declared purpose explicitly prohibits automatic deletion and promises a scan-and-review workflow. The supplied code instead immediately invokes Finder's empty-trash operation. Although trash cleanup relates to freeing disk space, executing deletion directly materially contradicts the stated safety and execution boundaries.
The cleanup targets relate to the declared purpose, but the behavior violates its central safety boundary. The executable rm -rf commands remove contents rather than merely analyze usage or generate a reviewable cleanup plan. The supplied chunk provides no confirmation mechanism or checks supporting its claim that cache deletion is safe. Sudo authentication, if prompted, is not a substitute for the promised review and confirmation workflow.
Automatic execution is not established, but the skill presents 'git gc --aggressive --prune=now' as safe and not deleting history without explaining its immediate pruning behavior. If followed, it can remove otherwise recoverable unreachable objects and increases corruption risk when concurrent processes write to the repository.
Removing a virtual environment is related to disk cleanup, but rm -rf ./venv performs deletion rather than analysis or reporting. The comment explaining that the environment can be rebuilt does not provide confirmation or enforce the declared safety workflow.
The targeted resources are consistent with Mac disk cleanup, but the execution behavior contradicts the explicit promise not to delete files automatically. If run as supplied, these commands perform deletion immediately; the cautionary comments do not enforce review or confirmation. The simulator command targets unavailable simulators, not all simulators as its comment suggests.
The document does not demonstrate automatic execution, but it recommends 'docker system prune -a --volumes' without explaining that eligible unused volumes may contain valuable persistent data. Docker's confirmation prompt does not establish that those resources are disposable, and the command can cause data loss if followed as generic cleanup advice.
The command permanently deletes every non-hidden entry matched under the user's cache directory and is presented as universally safe. Although cache cleanup is relevant to the skill, blanket deletion while applications are active can disrupt them or remove offline state, and the suggested recovery guarantee is too broad.
# 清空用户 Caches(安全)
rm -rf ~/Library/Caches/*
# 清空系统日志
sudo rm -rf /Library/Logs/*
Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).
# 清空用户 Caches(安全)
rm -rf ~/Library/Caches/*
# 清空系统日志
sudo rm -rf /Library/Logs/*
Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).
sudo rm -rf /Library/Logs/* rm -rf ~/Library/Logs/*
### 废纸篓彻底清空(命令行版)
Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).
# 清理 DerivedData(编译缓存,可自动重建)
rm -rf ~/Library/Developer/Xcode/DerivedData/
# 清理模拟器(谨慎,会删除所有模拟器数据)
xcrun simctl delete unavailable
In context, this command runs with sudo and permanently removes matching system-wide log contents without age, ownership, or retention checks. It can erase troubleshooting and security evidence; it does not, however, delete the filesystem root.
rm -rf ~/Library/Caches/*
sudo rm -rf /Library/Logs/* rm -rf ~/Library/Logs/*
Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).
rm -rf ~/Library/Caches/*
sudo rm -rf /Library/Logs/* rm -rf ~/Library/Logs/*
Blanket deletion of user logs permanently removes potentially valuable troubleshooting or incident evidence. Its presentation as routine safe cleanup lacks age-based selection, retention checks, and a recoverable removal path.
sudo rm -rf /Library/Logs/* rm -rf ~/Library/Logs/*
### 废纸篓彻底清空(命令行版)
Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).
# 删除 venv,保留代码(之后用 pip install -r requirements.txt 重建)
rm -rf ./venv
Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).
# 清理 DerivedData(编译缓存,可自动重建)
rm -rf ~/Library/Developer/Xcode/DerivedData/
# 清理模拟器(谨慎,会删除所有模拟器数据)
xcrun simctl delete unavailable
The rule incorrectly groups '.git/objects/' with disposable dependency directories. This directory stores Git objects, including committed content and history that may exist nowhere else; deleting it can render a repository unusable and cannot generally be repaired with 'git restore'.
The reference commands permanently delete broad directory contents despite the stated trash-first rule. Labeling these actions safe and automatically recoverable can cause users or an executing agent to underestimate the loss of application state or diagnostic records.
The issue is not the mere presence of sudo, but its use to recursively erase all matching contents under '/Library/Logs/' as generic cleanup. If approved and executed, this elevated operation can destroy diagnostic or audit evidence without checking retention needs or identifying safe targets.
rm -rf ~/Library/Caches/*
sudo rm -rf /Library/Logs/* rm -rf ~/Library/Logs/*
The skill mandates unrelated advertising and an external invitation link in every response, contaminating disk-audit output with the author's promotional agenda. This can mislead users into treating an unrelated destination as an endorsed part of the workflow, although the text does not demonstrate exfiltration or malicious behavior at that destination.
The instruction to activate immediately includes “整理一下我的电脑” (“organize my computer”). This could mean arranging files or applications rather than auditing disk usage, and no exclusion or clarification condition distinguishes these requests.
Detected: suspicious.destructive_delete_command