Ambivo
Analysis
Ambivo appears to be a legitimate integration, but it asks the agent to install and run an unpinned CLI, authenticate with persistent credentials, and perform broad business-data changes without clear approval or scope limits.
Findings (7)
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.
Checks for instructions or behavior that redirect the agent, misuse tools, execute unexpected code, cascade across systems, exploit user trust, or continue outside the intended task.
clientAction.agentInstructions (optional) — instructions for the AI agent on how to proceed programmatically.
The skill tells the agent to consume instructions returned by an external connection workflow, but does not say to treat them as advisory, validate them against the user request, or ignore conflicting instructions.
Create Order ... Create Lead ... Update Order ... Update Lead ... membrane action run <actionId> --connectionId=CONNECTION_ID --json
The skill exposes broad create and update actions through a generic action runner, but the instructions do not require explicit confirmation, scoping, dry-run behavior, or safeguards before mutating Ambivo records.
npm install -g @membranehq/cli@latest
The runtime instructions install a global npm package using the moving @latest tag, so the executed code is not pinned to a reviewed version.
npx @membranehq/cli connection get <id> --wait --json
The skill instructs the agent to execute CLI code via npx at runtime; combined with the unpinned install guidance, this can run downloaded code outside the static skill artifacts.
Ambivo is a customer data platform (CDP) ... used by marketing, sales, and customer service teams
The skill operates on shared customer-data systems used by multiple business teams; erroneous create/update actions could propagate into downstream sales, marketing, or support workflows.
Checks whether tool use, credentials, dependencies, identity, account access, or inter-agent boundaries are broader than the stated purpose.
Membrane handles authentication and credentials refresh automatically
The skill relies on authenticated Membrane/Ambivo account access with automatic credential refresh, but the artifacts do not define least-privilege scopes, credential lifetime, or boundaries on what the agent may do with that authority.
Checks for exposed credentials, poisoned memory or context, unclear communication boundaries, or sensitive data that could leave the user's control.
If no app is found, one is created and a connector is built automatically.
The skill uses Membrane as an external connection and connector layer, including automatic connector creation, so users should understand that Ambivo access and action mediation occur through that provider workflow.
