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 DMP batch-audience skill has a real business purpose, but it also adds persistent monitoring, credential storage, external notifications, and extra skill installs that require Review before use.
Only install after confirming you are comfortable granting this skill DMP account access, storing API credentials locally, creating or using scheduled monitors, and optionally sending task metadata to chat/email webhooks. Review and disable the bundled monitor service unless you explicitly need a resident background watcher, remove the preloaded monitor task, and prefer a secure secret store over pasting long-lived AK/SK into chat.
Mixing characters from multiple Unicode scripts in a single identifier is a common technique to create visually ambiguous tool names.
If the main realized behavior is background polling, notification, and local persistent configuration rather than the declared DMP task management, users may unknowingly authorize broader host access and outbound messaging. The mismatch is more dangerous here because the documented workflow already normalizes cron, file writes, and monitoring as mandatory.
If the main realized behavior is background polling, notification, and local persistent configuration rather than the declared DMP task management, users may unknowingly authorize broader host access and outbound messaging. The mismatch is more dangerous here because the documented workflow already normalizes cron, file writes, and monitoring as mandatory.
If the main realized behavior is background polling, notification, and local persistent configuration rather than the declared DMP task management, users may unknowingly authorize broader host access and outbound messaging. The mismatch is more dangerous here because the documented workflow already normalizes cron, file writes, and monitoring as mandatory.
If the main realized behavior is background polling, notification, and local persistent configuration rather than the declared DMP task management, users may unknowingly authorize broader host access and outbound messaging. The mismatch is more dangerous here because the documented workflow already normalizes cron, file writes, and monitoring as mandatory.
If the main realized behavior is background polling, notification, and local persistent configuration rather than the declared DMP task management, users may unknowingly authorize broader host access and outbound messaging. The mismatch is more dangerous here because the documented workflow already normalizes cron, file writes, and monitoring as mandatory.
If the main realized behavior is background polling, notification, and local persistent configuration rather than the declared DMP task management, users may unknowingly authorize broader host access and outbound messaging. The mismatch is more dangerous here because the documented workflow already normalizes cron, file writes, and monitoring as mandatory.
If the main realized behavior is background polling, notification, and local persistent configuration rather than the declared DMP task management, users may unknowingly authorize broader host access and outbound messaging. The mismatch is more dangerous here because the documented workflow already normalizes cron, file writes, and monitoring as mandatory.
If the main realized behavior is background polling, notification, and local persistent configuration rather than the declared DMP task management, users may unknowingly authorize broader host access and outbound messaging. The mismatch is more dangerous here because the documented workflow already normalizes cron, file writes, and monitoring as mandatory.
If the main realized behavior is background polling, notification, and local persistent configuration rather than the declared DMP task management, users may unknowingly authorize broader host access and outbound messaging. The mismatch is more dangerous here because the documented workflow already normalizes cron, file writes, and monitoring as mandatory.
If the main realized behavior is background polling, notification, and local persistent configuration rather than the declared DMP task management, users may unknowingly authorize broader host access and outbound messaging. The mismatch is more dangerous here because the documented workflow already normalizes cron, file writes, and monitoring as mandatory.
If the main realized behavior is background polling, notification, and local persistent configuration rather than the declared DMP task management, users may unknowingly authorize broader host access and outbound messaging. The mismatch is more dangerous here because the documented workflow already normalizes cron, file writes, and monitoring as mandatory.
If the main realized behavior is background polling, notification, and local persistent configuration rather than the declared DMP task management, users may unknowingly authorize broader host access and outbound messaging. The mismatch is more dangerous here because the documented workflow already normalizes cron, file writes, and monitoring as mandatory.
If the main realized behavior is background polling, notification, and local persistent configuration rather than the declared DMP task management, users may unknowingly authorize broader host access and outbound messaging. The mismatch is more dangerous here because the documented workflow already normalizes cron, file writes, and monitoring as mandatory.
If the main realized behavior is background polling, notification, and local persistent configuration rather than the declared DMP task management, users may unknowingly authorize broader host access and outbound messaging. The mismatch is more dangerous here because the documented workflow already normalizes cron, file writes, and monitoring as mandatory.
If the main realized behavior is background polling, notification, and local persistent configuration rather than the declared DMP task management, users may unknowingly authorize broader host access and outbound messaging. The mismatch is more dangerous here because the documented workflow already normalizes cron, file writes, and monitoring as mandatory.
If the main realized behavior is background polling, notification, and local persistent configuration rather than the declared DMP task management, users may unknowingly authorize broader host access and outbound messaging. The mismatch is more dangerous here because the documented workflow already normalizes cron, file writes, and monitoring as mandatory.
If the main realized behavior is background polling, notification, and local persistent configuration rather than the declared DMP task management, users may unknowingly authorize broader host access and outbound messaging. The mismatch is more dangerous here because the documented workflow already normalizes cron, file writes, and monitoring as mandatory.
If the main realized behavior is background polling, notification, and local persistent configuration rather than the declared DMP task management, users may unknowingly authorize broader host access and outbound messaging. The mismatch is more dangerous here because the documented workflow already normalizes cron, file writes, and monitoring as mandatory.
Skill contains instructions that could directly expose system prompts, internal rules, or hidden instructions to users or external parties.
if not has_content:
rules.append({"op": "noop", "rule": {"audience": [], "tag": []}})
return rules
# 每个标签单独一个rule(框间AND/NOT),第一个rule带audience
for i, tag in enumerate(tags):
Skill contains instructions that could directly expose system prompts, internal rules, or hidden instructions to users or external parties.
if not has_content:
rules.append({"op": "noop", "rule": {"audience": [], "tag": []}})
return rules
# 每个标签单独一个rule(框间AND/NOT),第一个rule带audience
for i, tag in enumerate(tags):
The skill describes capabilities that imply shell, network, and file read/write access, but it does not declare any tool scope or permission boundary. That makes the effective privilege surface opaque to users and reviewers, increasing the risk of unintended command execution, local file modification, secret handling, and external network calls.
The skill offers automatic installation of another skill via terminal command without clearly emphasizing that this downloads and installs code onto the system. Users may consent without understanding the system-modifying and supply-chain implications.
The skill performs local installation of packages/skills through terminal commands, which is system-modifying behavior beyond the core batch-packaging purpose. Invoking installers from a business workflow increases the risk of unauthorized code download and execution on the host.
The local operation-password system is unrelated to the DMP business function and stores only an MD5 hash in the same credential context. MD5 is unsuitable for password storage, and adding ad hoc authentication logic increases the chance of weak, misleading security controls around sensitive operations.