Tp4
- Category
- MCP Tool Poisoning
- Confidence
- 95% confidence
- Finding
声明描述的是一个较完整的多平台自动回复系统,而代码仅提供回复结构模板与格式建议的本地CLI脚本。它没有接入任何平台,也没有监听、触发、发送回复的能力;也未进行关键词规则匹配。所谓AI生成仅是返回固定占位文本“[AI根据上下文自动生成]”。因此代码行为与声明的主要用途存在实质差异,属于描述明显夸大功能的情况。
- Content
Security audit
Security checks for vulnerabilities and agentic risk
This is a Chinese-language auto-reply template helper with no hidden data access or execution, though it overstates how much automation and AI generation it actually implements.
Use this as a template library and reply-format helper, not as a ready-to-run automation system. Before deploying any keyword rules to real customer or public channels, narrow generic triggers like price and booking terms, review platform policy compliance, and manually verify generated copy.
声明描述的是一个较完整的多平台自动回复系统,而代码仅提供回复结构模板与格式建议的本地CLI脚本。它没有接入任何平台,也没有监听、触发、发送回复的能力;也未进行关键词规则匹配。所谓AI生成仅是返回固定占位文本“[AI根据上下文自动生成]”。因此代码行为与声明的主要用途存在实质差异,属于描述明显夸大功能的情况。
Without declared permissions the skill's intent is opaque and cannot be validated.
Overly broad trigger phrases can cause the skill to activate on ordinary user requests outside the intended context, increasing the chance of unintended prompt injection surface, incorrect workflow selection, or disclosure of irrelevant canned instructions. In an assistant environment with multiple skills, ambiguous activation can override more appropriate behaviors and lead to unsafe or confusing responses.
The natural-language description, usage guidance, triggers, and examples are all presented as Chinese-only operational guidance, with no indication that the user may choose another language or locale. This can constitute a language/locale policy issue when the skill implicitly enforces a single language without opt-in.
The instruction to run whenever the user has an 'auto-reply need' is vague and effectively self-expanding, which can make the skill activate in situations where the user only seeks general advice, messaging help, or unrelated automation. This broad activation increases the likelihood of unintended behavior and can be abused to steer the assistant into a narrower workflow than the user intended.
This manifest-style JSON uses a very generic activation keyword, "预约", as an auto-reply trigger. Because the file does not define context limits, exclusions, or negative examples, ordinary conversation containing this common word could invoke the skill unintentionally.
Keywords such as "价格", "收费", "多少钱", "预约", and "体验" are broad everyday terms that can appear in many unrelated conversations. The configuration does not provide scoping rules or negative examples to distinguish intended service inquiries from incidental mentions.
The Feishu keyword replies activate on short common terms like "价格", "收费", and "预约" with no contextual boundaries. In a chat environment, these broad terms are likely to collide with ordinary discussion and trigger unintended responses.
The module docstring and generate_reply docstring state that the script generates suitable replies based on platform, message, and tone, suggesting actual reply generation. In practice, the code always sets suggested_reply to the fixed placeholder "[AI根据上下文自动生成]" and only assembles metadata and tips, so the documentation overstates what the implementation does.
The file’s natural-language description and all user-facing defaults are written exclusively in Chinese, and the script constrains platform/tone values to Chinese-only options. There is no indication that the skill is region-specific or that users may opt into another language, which can violate language/locale policy requirements.
Natural-language strings throughout the configuration force Chinese-language interactions, and there is no indication that users can opt into another language or that the skill is intentionally limited to a Chinese-language audience. This may violate language/locale policy when used in broader multilingual environments.
No suspicious patterns detected.