Email Sender Policy

ReviewAudited by ClawScan on May 10, 2026.

Overview

This is a disclosed Gmail-sending skill that uses a Maton API key, so it is purpose-aligned but should be treated as real email-sending authority.

Install only if you intend to let this skill send real Gmail messages through Maton. Before live use, set MATON_API_KEY carefully, confirm the connected Gmail account, preview recipients and message content, and use --test for dry runs.

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.

Medium

#ASI03: Identity and Privilege Abuse

What this means

If invoked with valid credentials, the skill can send email from the connected Gmail account.

Why it was flagged

The skill uses a Maton API key to act through the user's Gmail connection. This is expected for sending Gmail, but it is delegated account authority.

Skill content

const MATON_API_KEY = process.env.MATON_API_KEY; ... 'Authorization': `Bearer ${MATON_API_KEY}`

Recommendation

Use a dedicated or appropriately scoped API key if available, keep the key secret, and verify the Gmail connection before sending.

Medium

#ASI02: Tool Misuse and Exploitation

What this means

A mistaken invocation could send an unintended message or send it to unintended recipients.

Why it was flagged

The code performs the live Gmail send operation directly when not in --test mode. This matches the purpose, but outbound email is a high-impact action.

Skill content

const response = await fetch(url, { method: 'POST', ... body: payload });

Recommendation

Use --test or otherwise preview recipients, subject, body, cc, and bcc before allowing live sends.

Low

#ASI04: Agentic Supply Chain Vulnerabilities

What this means

Users may not realize before installation that the skill needs a Node runtime and a Maton API key for live sending.

Why it was flagged

The registry-level requirements under-declare what the included files use: _meta.json and code require node and MATON_API_KEY. The behavior is documented elsewhere, but installers may not surface it clearly.

Skill content

Required env vars: none; Primary credential: none; Required binaries ... none

Recommendation

Treat MATON_API_KEY and Node as required setup items, and maintainers should update registry metadata to match the included files.