Influxdb Cloud
Security checks across static analysis, malware telemetry, and agentic risk
Overview
This InfluxDB Cloud skill is coherent, but it gives the agent broad authenticated API access that can modify or delete cloud resources without clear approval or scope limits.
Install only if you are comfortable granting Membrane-mediated access to your InfluxDB Cloud account. Use least-privilege credentials, pin or verify the CLI package if possible, and require explicit confirmation before any write, delete, user, authorization, secret, task, bucket, or organization changes.
Static analysis
No static analysis findings were reported for this release.
VirusTotal
VirusTotal findings are pending for this skill version.
Risk analysis
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.
If connected with a privileged account, the agent could change or delete InfluxDB Cloud resources while completing a task.
This exposes a raw authenticated API escape hatch that can perform modifying or destructive operations, without visible guardrails requiring user confirmation or limiting which endpoints may be used.
When the available actions don't cover your use case, you can send requests directly to the InfluxDB Cloud API through Membrane's proxy... HTTP method (GET, POST, PUT, PATCH, DELETE).
Prefer listed actions and read-only queries; require explicit user confirmation for POST, PUT, PATCH, DELETE, user, authorization, secret, task, bucket, or organization changes.
The skill may act with the privileges granted to the Membrane/InfluxDB connection.
The skill intentionally delegates authentication to Membrane and may reach sensitive account objects. This is expected for the integration, but the artifacts do not define least-privilege scopes.
Membrane handles authentication and credentials refresh automatically... InfluxDB Cloud Overview ... User ... Authorization ... Secret
Use a least-privilege InfluxDB connection or token, avoid admin credentials unless necessary, and review what Membrane is authorized to access.
A future CLI version or npm package issue could affect behavior outside what was reviewed here.
The setup uses a globally installed, unpinned npm CLI. This is user-directed and central to the skill, but the exact package version is not fixed in the reviewed artifacts.
npm install -g @membranehq/cli@latest
Install from the expected publisher, consider pinning a known version, and review the CLI package before using it with sensitive cloud credentials.
InfluxDB request details and responses may pass through Membrane rather than only between the user and InfluxDB.
InfluxDB API calls are routed through Membrane as a gateway. This is disclosed and purpose-aligned, but it is an important data and credential boundary.
send requests directly to the InfluxDB Cloud API through Membrane's proxy... injects the correct authentication headers
Review Membrane's data handling policy and avoid routing unnecessary sensitive data through the integration.