Tmp.Qs5EOZDgAo
WarnAudited by ClawScan on May 15, 2026.
Overview
This Zola wedding-planning integration is purpose-aligned, but it asks you to run an external MCP package and give it a long-lived Zola cookie/token that can read and change important account data.
Use this only if you trust the external zola-mcp package and are comfortable giving it a long-lived Zola token. Before installing, review the source, pin a known version, protect the token like a password, and require the agent to ask before making any changes to your Zola account.
Findings (3)
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 remote package outside the reviewed artifacts could receive the Zola token and operate as an MCP server for the agent.
The registry provides no install spec or reviewed code files, but the skill tells users to install and run an external npm/GitHub MCP package. That package would be the code handling the user's Zola access.
"command": "npx", "args": ["-y", "zola-mcp"] ... "git clone https://github.com/chrischall/zola-mcp" ... "npm install && npm run build"
Only install after reviewing the npm/GitHub source, pinning a trusted version, and confirming the package provenance.
Anyone or anything with this token may be able to access private wedding data and perform account actions until the token expires or is revoked.
The skill requires a long-lived Zola session/refresh token captured from a browser cookie. This grants durable account access and is not declared in the registry requirements as a required env var or primary credential.
"ZOLA_REFRESH_TOKEN" | Yes | Mobile API JWT refresh token (~1 year lifetime) ... "captures the `usr` cookie (a ~1-year JWT)"
Treat the token like a password: store it securely, avoid sharing logs or config files, rotate/revoke it if exposed, and prefer a scoped official OAuth flow if available.
The agent could accidentally or prematurely change guest lists, seating, budget values, vendor bookings, or event details in the user's Zola account.
The exposed tools include multiple account-changing operations for vendors, budgets, guests, seating, and events, but the instructions do not define explicit confirmation or containment requirements before writes or removals.
`add_vendor`, `update_vendor`, `remove_vendor`, `update_budget_item`, `add_guest`, `remove_guest`, `assign_seat`, `update_event`
Require explicit user confirmation before any add, update, delete, booking, seating, or event-change action, and keep a record of changes made.