ClawHub
Back to skill

Security audit

Mx Data

Security checks for vulnerabilities and agentic risk

Overview

This skill transparently queries Eastmoney financial data with a user-provided API key and saves the returned results locally.

Install only if you trust the claimed Eastmoney/Miaoxiang provider and are comfortable using an MX_APIKEY with this skill. Do not include sensitive internal financial questions or secrets in queries unless sharing them with that API provider is acceptable, and protect or delete the local output directory if saved raw results are sensitive.

SkillSpector

Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • MCP Least PrivilegeUnderdeclared Capability, Wildcard Permission, Missing Permission Declaration
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (2)

Lp3

Medium
Category
MCP Least Privilege
Confidence
88% confidence
Finding
The skill documentation indicates access to environment variables, file output, and outbound network requests, but it does not declare corresponding permissions. This creates a transparency and governance gap: a reviewer or runtime may underestimate what the skill can access and do, especially since it handles an API key and writes raw query results to disk.

External Transmission

Medium
Category
Data Exfiltration
Content
> - **凭据保护**: API Key 仅通过环境变量 `MX_APIKEY` 在服务端或受信任的运行环境中使用，不会在前端明文暴露。

```javascript
curl -X POST --location 'https://mkapi2.dfcfs.com/finskillshub/api/claw/query' \
--header 'Content-Type: application/json' \
--header 'apikey: YOUR_API_KEY' \
--data '{"toolQuery": "东方财富最新价"}'
Confidence
81% confidence
Finding
The skill sends user-provided query text and an API key to an external service (`mkapi2.dfcfs.com`). In context this is expected functionality, but it is still a real data-exposure boundary: sensitive prompts, internal company questions, or regulated financial queries could be transmitted off-platform, and the API key could be mishandled if logs, proxies, or client-side usage are not tightly controlled.

Static analysis

No suspicious patterns detected.