ClawHub
Back to skill

Security audit

Google Calendar

Security checks for vulnerabilities and agentic risk

Overview

Calendar actions have clear approval safeguards, but setup can introduce persistent agent skills beyond Google Calendar without explaining that effect.

Review the CLI setup before installing. Prefer a verified, user-managed CLI installation and decide whether it may install or synchronize skills in your other agent applications. Upstream documents OO_SKILLS_SYNC_DISABLED=1 to disable startup skill synchronization: [CLI controls](https://github.com/oomol-lab/oo-cli/blob/main/docs/commands.md). Also review the Google Calendar permissions granted through OOMOL. Calendar mutation approvals are explicit, but the remote installer and connector implementation were not verified.

A.I.G

Vulnerability Patterns
  • Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
  • Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
  • Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
  • Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs

SkillSpector

Vulnerability Patterns
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
  • MCP Tool PoisoningHidden Instructions, Unicode Deception, Parameter Description Injection
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
Findings (3)

Description-Behavior Mismatch

High
Category
MCP Tool Poisoning
Confidence
95% confidence
Finding

The visible behavior is remote software installation rather than Google Calendar access. Installation can be a supporting implementation detail, but this chunk provides no evidence linking the Oomol CLI installer to the declared functionality. The downloaded script is not supplied, so its further behavior cannot be assessed.

Content

No source excerpt is available for this finding.

External Script Fetching

High
Category
Supply Chain
Confidence
98% confidence
Finding

The setup instructions pipe a remotely fetched, mutable script directly into Bash without checking a trusted signature or independently verified digest; the PowerShell alternative uses the same fetch-and-execute pattern. Compromise of the distribution endpoint or release pipeline could therefore execute arbitrary code with the invoking user's privileges. Restricting setup to a missing-CLI error reduces exposure, but neither that condition nor HTTPS verifies the integrity of the installer itself.

Content

Scanner excerpt · SKILL.md (reported line 92)May include surrounding context.

Autonomous Decision Making

Medium
Category
Excessive Agency
Confidence
80% confidence
Finding

Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.

Content

Scanner excerpt · SKILL.md (reported line 113)May include surrounding context.

md
- **`OOMOL_INSUFFICIENT_CREDIT`** — OOMOL billing stop. Recharge at `https://console.oomol.com/billing/token-recharge` before retrying.

- **HTTP 402 without `OOMOL_INSUFFICIENT_CREDIT`** — the third-party account itself has no active plan or credit. Report the provider error message as is; do not ask the user to recharge OOMOL.

## Resources