Marketo
Security checks across malware telemetry and agentic risk
Overview
This is a coherent Marketo integration, but it relies on Membrane OAuth/CLI access and can perform powerful Marketo actions, so users should approve destructive or campaign-changing operations.
Install only if you trust Membrane and the Membrane CLI. Connect the correct Marketo account, use the least privilege available, explicitly review any delete/update/list-change/campaign-trigger or proxy request before it runs, and revoke the connection when you no longer need it.
VirusTotal
65/65 vendors flagged this skill as clean.
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.
A mistaken or overly broad action could delete or change lead records or trigger marketing workflows in the connected Marketo account.
The skill documents Marketo actions that can mutate business/customer data or trigger campaigns through a generic CLI runner. This is aligned with a Marketo management integration, but users should treat these operations as high-impact.
Trigger Campaign | trigger-campaign | Trigger a smart campaign for specified leads. ... Delete Leads | delete-leads | Delete one or more leads by their IDs ... membrane action run <actionId> --connectionId=CONNECTION_ID --json
Confirm the exact connection, action, inputs, and expected impact before running create, update, delete, list-change, or campaign-trigger actions.
The agent may be able to call Marketo endpoints beyond the listed popular actions, limited by the connected account's permissions.
The direct API proxy is a broad escape-hatch capability. It is disclosed and purpose-aligned for advanced Marketo use, but it can bypass more structured action workflows.
When the available actions don't cover your use case, you can send requests directly to the Marketo API through Membrane's proxy.
Use the structured Membrane actions where possible, and require explicit user approval for direct proxy calls that write, delete, or trigger external effects.
The integration can act with the privileges of the Marketo connection the user authorizes.
The skill relies on delegated authentication for Membrane/Marketo access. This is expected for the integration, but it means the connected account's permissions matter.
Membrane handles authentication and credentials refresh automatically
Connect only the intended Marketo account, prefer least-privileged access where available, and revoke the Membrane connection when it is no longer needed.
Future CLI versions could behave differently from the version implied at review time.
The setup asks the user to install a global CLI from npm using the moving @latest tag. This is central to the skill's purpose, but the exact installed version may change over time.
npm install -g @membranehq/cli@latest
Install from the official package source, consider pinning a known version, and keep the CLI updated deliberately rather than unexpectedly.
Marketo data and API interactions may pass through Membrane infrastructure as part of the integration.
Marketo requests and responses are routed through Membrane as an external integration gateway. This is disclosed and expected, but it is an important data boundary.
send requests directly to the Marketo API through Membrane's proxy
Use this skill only if you trust Membrane with the relevant Marketo data and review Membrane's security/privacy practices for your organization.