Security audit
Security checks for vulnerabilities and agentic risk
The skill is a coherent n8n workflow-management helper, but it grants broad workflow-changing authority through a bearer token without enough safety guidance.
Review this skill before installing. Only use it with an n8n MCP token you are willing to grant workflow-management authority to, store that token as a secret, and confirm before creating, publishing, executing, updating, or archiving workflows because those actions can persistently change your automation environment.
The skill describes use of an Authorization bearer token and tells the user to obtain and configure it, but does not warn that the token is a sensitive credential that grants control over local n8n workflows. If exposed in prompts, logs, shell history, or copied examples, the token could be reused to create, execute, publish, or delete workflow-related assets.
The skill instructs users to publish, execute, update, and archive workflows, all of which can alter local automation behavior and stored workflow state, but it does not warn that these are state-changing operations. In this context, workflows may trigger network calls, scheduled jobs, or modify business logic on the host n8n instance, so omission of a clear warning increases the risk of unintended operational changes.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
TOKEN="<n8n-mcp-token>"
curl -s -X POST http://localhost:5678/mcp-server/http \
-H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"<TOOL>","arguments":{...}}}'
The natural-language instructions throughout the skill are presented only in Chinese, which can impose a language constraint on users without opt-in. The file does not indicate that the language choice is optional or required for a justified region-specific reason.