Security audit
Security checks for vulnerabilities and agentic risk
This skill is a disclosed FBox industrial IoT MCP integration, but users should treat its device-control and API-key access as sensitive.
Install only if you administer the relevant FBox environment. Use a least-privilege API key, keep it out of source control and logs, rotate it periodically, and require human review for PLC writes, alarm acknowledgments, and VNC sessions on production equipment.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
macOS / Linux：
curl -X POST https://fboxmcp.fbox360.com/api/apikey/generate \
-H "Content-Type: application/json" \
-d '{"clientId": "your-client-id", "clientSecret": "your-client-secret"}'
The guide instructs users to place a long-lived API key directly into environment variables and request headers, but provides no warning that the credential is sensitive, persistent, and should be rotated or scoped carefully. In an industrial IoT context, compromise of this bearer token could allow unauthorized access to device status, telemetry, alarms, PLC point operations, or remote monitoring functions.
The README advertises real-time PLC point writes, alarm acknowledgment, and remote VNC access without any visible warning, confirmation guidance, or safety constraints for actions that can affect live industrial systems. In an industrial IoT context, normalizing control actions as routine chat operations increases the chance of unsafe or unintended operator actions, which can lead to process disruption, concealment of active alarms, or unauthorized remote interaction with equipment.
The trigger description is broad and includes generic industrial terms like device status, sensor values, alarms, remote monitoring, and VNC, which can cause the skill to activate for loosely related requests. In this skill, accidental activation is more dangerous than usual because the tool can read operational telemetry and initiate sensitive actions such as alarm confirmation, PLC point writes, and opening remote monitoring sessions.
L038 规定“展示给用户时必须转为北京时间（UTC+8）”，这是对所有用户统一施加的地区/时区要求，没有提供用户选择或基于用户所在地的适配机制。该类强制 locale 约束属于自然语言层面的地区策略限制。
The skill documents retrieval of system-level device settings such as IP address, subnet mask, gateway, DNS, firmware version, and dual-NIC details without any warning that these are sensitive infrastructure details. In an OT/IoT environment, this information can materially assist reconnaissance, lateral movement planning, network mapping, and targeting of vulnerable firmware or exposed services.
The documentation exposes capabilities to retrieve precise device geolocation and address information without any warning, consent requirement, or guidance on limiting access. In an industrial IoT context, location data can reveal facility locations, customer sites, and operational footprints, which could aid physical targeting, stalking, or infrastructure mapping if surfaced to an unauthorized or over-broad audience.
This markdown file presents all operational guidance and parameter descriptions exclusively in Chinese. Under the stated policy, forcing a specific language without user opt-in or a documented justification is a natural-language policy violation.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
curl https://<fboxmcp-host>/health
返回 200 OK 表示服务正常。
All user-facing instructions in the file are presented only in Chinese, and there is no indication that the skill is region-specific or that users may choose another language. This can violate language/locale policy where user-facing skill materials should not force a single language without opt-in or justification.
The README states that displayed times are automatically converted to Beijing time (UTC+8), which imposes a locale-specific presentation by default. No user choice, opt-in, or justification for this fixed locale behavior is provided in the file.
This markdown file presents all operational instructions, parameter descriptions, and usage guidance only in Chinese. The policy requires flagging language or locale constraints when a skill forces a specific language without user opt-in, and no alternative language option or justification is provided here.
The document presents all user-facing instructions and field descriptions in Chinese and does not mention language selection or locale scoping. Under SQP-3, forcing a specific language without opt-in can be a natural-language policy concern unless the locale constraint is clearly documented and justified.
L155-L156 明确写明安装 Skill 后“自动转为北京时间（UTC+8）”，属于固定语言/区域格式行为。根据规则，若未提供用户选择或未说明这是特定区域场景下的合理限制，可视为自然语言层面的 locale policy violation。