Security audit
Security checks for vulnerabilities and agentic risk
This is a coherent n8n API helper skill, but users should treat its workflow, webhook, retry, credential, role, and delete examples as live administrative actions.
Install only if you want your agent to help administer n8n through the public API. Use a least-privileged n8n API key where possible, confirm the target instance before any create/update/delete/activate/deactivate/retry/webhook action, and prefer test workflows or a test instance for experiments.
The skill description is broad enough to invite use for generic 'automation tasks' rather than clearly constraining operations to n8n administration. In an agent setting, that can cause over-invocation and lead the model to perform workflow creation, publishing, or triggering actions on a live n8n instance when the user's request was ambiguous.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
curl -s -H "X-N8N-API-KEY: $N8N_API_KEY" "$N8N_API_BASE_URL/workflows/{id}"
The activate/deactivate examples document live state changes without warning that they can immediately enable or disable production automations. In an agentic context, this increases the chance of unintended service disruption or unreviewed publication of workflows to live environments.
The webhook trigger examples directly invoke workflow logic and can execute arbitrary downstream actions configured in n8n, potentially affecting external services or data. Because the examples lack a warning, an agent may trigger production or test webhooks casually, causing real-world side effects on live systems.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
| jq '.data[] | {id, workflowId, status, startedAt}'
curl -s -H "X-N8N-API-KEY: $N8N_API_KEY"
"$N8N_API_BASE_URL/executions?status=error&limit=5"
Retrying an execution can replay workflow steps that send emails, write records, call third-party APIs, or perform other irreversible side effects. Without an explicit warning, an agent may treat retry as a harmless troubleshooting action and unintentionally duplicate actions against live systems.
This markdown file documents actions such as deleting users, workflows, credentials, variables, projects, execution records, and rows, as well as role changes, transfers, activation/deactivation, and source-control pulls. Under the markdown-specific SQP-2 criteria, the file should warn that these operations can affect user data, access, or system state, but it provides no cautionary language beyond endpoint descriptions.
No suspicious patterns detected.