Undeclared Tool Scope
- Category
- MCP Least Privilege
- Confidence
- 70% confidence
- Finding
Without declared permissions the skill's intent is opaque and cannot be validated.
- Content
Security audit
Security checks for vulnerabilities and agentic risk
This is a coherent thumbnail and cover-design helper with optional local formatting scripts and no evidence of hidden network, credential, persistence, or destructive behavior.
Installers should treat this as a design-production helper. Before using portrait or reference-image workflows, confirm you have consent and usage rights, and review generated prompts/layouts to avoid copying protected brand assets or misleading viewers. Non-Chinese users may need to ask explicitly for localized output.
Without declared permissions the skill's intent is opaque and cannot be validated.
The skill states that it will output Chinese title layout plans for downstream tools, and the rest of the document is written as mandatory Chinese-language operating guidance. There is no indication that users may request another language or locale, which creates a language policy concern under the rule for forced language without opt-in.
This markdown skill presents its instructions and labels exclusively in Chinese, which can impose a specific language on users without opt-in. The policy allows fixed language only when choice is offered or the locale constraint is clearly justified, neither of which appears in the file.
This markdown file contains end-user skill instructions and content exclusively in Chinese, with no indication that the user can choose another language or that the skill is intentionally limited to a Chinese-speaking context. Under the language/locale policy, forcing a specific language without user opt-in is a natural-language policy concern.
This JSON content consistently specifies titles, notes, emotions, and gesture guidance in Chinese across multiple entries, including platforms that are typically multilingual or English-oriented such as YouTube. Because the file provides no indication that Chinese is optional, user-selected, or required by a region-specific use case, it presents a natural-language locale constraint without opt-in.
The entire markdown file, including the title and processing instruction, is written only in Chinese and directs the skill to produce outputs in that language context. There is no indication that the user can choose another language or that the Chinese-only constraint is a documented region-specific requirement.
This JSON file contains user-facing natural-language output in Chinese in the notes array, but nothing in the file indicates that the skill is Chinese-only, region-specific, or that the user opted into that locale. That creates a language/locale policy concern because the output appears to force a specific language choice.
This markdown file contains user-facing natural language only in Chinese, and there is no indication that the user opted into that language or that the skill is intentionally limited to a Chinese-speaking region. Under the policy, forcing a specific language without user opt-in is a natural-language policy violation.
The title and section labels are written in Chinese, and line L52 explicitly specifies a general Chinese prompt section while the template provides no opt-in or language-selection guidance. This creates a natural-language locale policy concern because it appears to require Chinese output by default rather than letting the user choose their preferred language.
This JSON includes a natural-language constraint in the negative prompt forbidding 'Chinese text', while the rest of the content is written in Chinese and does not provide any user opt-in or locale selection. That creates a language-policy inconsistency by implicitly enforcing a specific language/locale behavior without documented choice or justification.
This markdown file contains user-facing instructions exclusively in Chinese and does not indicate that the user can choose another language or that the skill is intentionally limited to a Chinese-speaking audience. Under the stated policy, forcing a specific language without user opt-in is a natural-language policy violation.
This markdown file is written primarily for a Chinese-language platform and audience, with headings and core content in Chinese, while also embedding English prompt text. The skill does not state that language should be selected based on user preference or provide an explicit opt-in for locale, which can be read as forcing a specific language/locale workflow.
The script defines title categories, suggestions, defaults, and generated markdown content entirely in Chinese, including the final output instructions. This imposes a specific language/locale on all users without any opt-in or documented regional constraint, which matches the language policy violation criteria.
The file description explicitly defines a 'universal Chinese prompt' as a standard output component. This imposes a specific language choice in the generated artifact without any visible user preference, opt-in, or justification for why Chinese must be included by default.
This markdown file uses only Chinese headings and field labels, which effectively forces a specific language for users completing the intake form. The policy allows locale constraints only when they are optional or clearly justified, but no language choice or region-specific rationale is provided here.
This CSV includes multiple natural-language title entries written in Chinese, but the file provides no surrounding instruction or metadata indicating that Chinese is an intentional, user-selected locale. Under the policy, forcing or assuming a language without opt-in can be a natural-language policy concern.