Flowise

PassAudited by ClawScan on May 1, 2026.

Overview

This is a coherent Flowise REST API helper, but users should protect the Flowise API key and be careful with session memory, uploads, and any action-capable Flowise flows.

Before installing, confirm that the Flowise server URL is trusted, protect the API key, and avoid sending sensitive files or prompts unless the Flowise instance is meant to receive them. Be especially cautious with configured flows that can execute scripts, control devices, or retain conversation memory.

Findings (4)

Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.

What this means

The agent may transmit your Flowise requests and selected data to the configured Flowise instance.

Why it was flagged

The skill authorizes shell-based REST calls to the configured Flowise server. This is central to the skill, but it means user prompts, parameters, and uploads can be sent to that server.

Skill content
3. Use `exec` with `curl` to call the API
Recommendation

Use only trusted Flowise URLs and review the selected flow before sending sensitive data or invoking flows that may perform actions.

What this means

Anyone who can read or misuse the configured API key may be able to access your Flowise workflows.

Why it was flagged

The skill expects a Flowise API key for authenticated deployments. This is expected for the integration, but it is still a credential that can grant access to the Flowise instance.

Skill content
- API Key: your-api-key-here
Recommendation

Store the API key carefully, avoid sharing TOOLS.md, and use a least-privilege or revocable Flowise key when possible.

What this means

Past conversation content may influence later Flowise responses if the same session is reused.

Why it was flagged

The skill supports Flowise conversation memory through session IDs, so prior context may be reused by the Flowise workflow.

Skill content
`sessionId` | string | Session ID for conversation memory |
Recommendation

Use separate session IDs for unrelated tasks and avoid putting sensitive information into persistent Flowise sessions unless intended.

What this means

If a configured Flowise flow executes scripts or controls devices, invoking it could trigger real actions outside the chat.

Why it was flagged

The documentation shows that some configured Flowise flows may accept a script-to-execute and an optional device parameter. This appears flow-specific and disclosed, not hidden local execution by the skill.

Skill content
form格式: `script`=要执行的脚本, `device`=设备(可选)
Recommendation

Require explicit user confirmation before sending script or device parameters, and review the target flow, script, and device carefully.