T09 · Insecure Skill Coding Practices
- Location
mcp.json:4- Finding
Hardcoded Bearer Credential Exposed in MCP Configuration
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This hotel-search skill is not plainly malicious, but it needs review because it ships a reusable bearer credential and includes unpinned local server setup instructions.
Review before installing. Rotate or remove the packaged bearer token, use per-user secrets instead, avoid sending sensitive details in raw hotel queries, and only run the optional local server from a pinned and reviewed revision with locked dependencies.
mcp.json:4Hardcoded Bearer Credential Exposed in MCP Configuration
SKILL.md:22Mandatory Transmission of Unredacted User Queries to a Third-Party Service
README_EN.md:229Mutable Remote Repository Is Downloaded and Executed Without Integrity Verification
README_EN.md:235Dependency Installation Lacks Version and Integrity Controls
The file embeds a live-looking Bearer token directly in the MCP configuration, which exposes a reusable secret to anyone who can read the skill package. An exposed token can be copied and used to access the remote MCP service as this skill, potentially leading to unauthorized API use, data access, quota exhaustion, or billing abuse. The hotel-search context does not reduce risk; because this token authorizes external service access, bundling it in a distributable skill makes exploitation straightforward.
The README states that the language parameter defaults to zh_CN, which imposes a specific locale unless the caller explicitly overrides it. This is a natural-language locale policy concern because the documentation does not present the default as optional or ask for user preference first.
No suspicious patterns detected.