T09 · Insecure Skill Coding Practices
- Location
SKILL.md:36- Finding
API Key Exposed Through MCP URL Query Parameter
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill matches its stated social-media publishing purpose, but its API-key setup method risks exposing credentials for accounts that can publish public posts.
Prefer the OAuth setup and avoid the API-key URL method. Install only if you are comfortable giving the agent the ability to create, schedule, upload media for, and delete social-media resources when you explicitly ask it to, and review target accounts, content, and schedule carefully before public posting.
SKILL.md:36API Key Exposed Through MCP URL Query Parameter
The skill advertises very broad activation criteria such as 'use whenever the user wants to post, schedule, queue, cross-post, bulk-schedule, draft, or auto-publish social content,' which increases the chance the agent invokes it in loosely related contexts. Because this skill can trigger real external publishing actions, overbroad routing materially raises the risk of unintended posting to public third-party platforms.
The skill enables publishing and auto-publishing to multiple third-party social networks, but the description does not prominently warn that content will be transmitted externally and may become publicly visible. In a tool that can make irreversible public-facing changes, lack of up-front disclosure increases the risk of users or orchestration layers invoking it without appreciating the external impact.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
openclaw mcp add woopsocial \
--url https://api.woopsocial.com/mcp \
--transport streamable-http \
--auth oauth
The documentation instructs users to place an API key directly in the MCP URL query string. Query-parameter secrets are commonly exposed through shell history, process listings, logs, config files, screenshots, and proxy/server logging, making credential leakage significantly more likely than header- or secret-store-based authentication.
openclaw mcp add woopsocial \
--url https://api.woopsocial.com/mcp?api_key=YOUR_API_KEY \
--transport streamable-http
No suspicious patterns detected.