ZOOM Meeting Admin

• Outcome: Pass
• Latest audit: Jun 5, 2026 · 2:22 PM UTC
• Version: 1.0.3

Overview

This skill is a disclosed Zoom admin helper that uses local Zoom OAuth credentials for a limited set of meeting, user, and recording actions, but those credentials and write/delete permissions are sensitive.

Install only if you are comfortable giving an agent access to a Zoom Server-to-Server OAuth app. Use a dedicated Zoom app, grant only the scopes you need, keep .env and ~/.zoom-s2s-token.json private with restrictive permissions, verify .env is ignored by git, and require explicit human approval before creating or deleting meetings.

SkillSpector

By NVIDIA

Vulnerability Patterns

• Data Exfiltration: External Transmission, Env Variable Harvesting, File System Enumeration
• Privilege Escalation: Excessive Permissions, Sudo/Root Execution, Credential Access
• MCP Tool Poisoning: Hidden Instructions, Unicode Deception, Parameter Description Injection
• Prompt Injection: Instruction Override, Hidden Instructions, Exfiltration Commands
• Supply Chain: Unpinned Dependencies, External Script Fetching, Obfuscated Code

Findings (6)

Tp4

High

• Category: MCP Tool Poisoning
• Confidence: 88% confidence
• Finding: The skill claims that create_meeting and delete_meeting require explicit user confirmation, but the documented CLI examples show create_meeting can be invoked directly without any technical guardrail. If an agent follows the script interface instead of the prose policy, it could create meetings without confirmed user consent, causing unauthorized external actions in a real account.

Missing User Warnings

Low

• Confidence: 88% confidence
• Finding: The README instructs users to place high-value Zoom Server-to-Server OAuth credentials in a local .env file but gives only a minimal 'do NOT commit to git' note and does not clearly warn about the consequences of credential leakage. Because these credentials can grant account-level API access for meetings, recordings, and user data, insufficient secret-handling guidance increases the chance of accidental exposure through repos, logs, screenshots, or copied examples.

Missing User Warnings

Medium

• Confidence: 84% confidence
• Finding: The README instructs users to place high-value Server-to-Server OAuth credentials in a local .env file but does not emphasize their sensitivity, storage precautions, or rotation requirements. Because these credentials can grant broad account-level Zoom access, weak handling increases the risk of accidental exposure through source control, logs, backups, or shared workstations.

Missing User Warnings

Medium

• Confidence: 80% confidence
• Finding: The README lists a destructive delete-meeting scope without warning that the skill can modify or remove real Zoom resources. Even though the broader skill context says delete actions require explicit confirmation, omitting that warning in setup documentation may cause users to grant powerful scopes without understanding the operational risk.

Credential Access

High

• Category: Privilege Escalation

Content

---
name: zoom-meeting-admin
allowed-tools: Bash(python3:*) Bash(ls:*) Bash(cat:*) Read
compatibility: Requires Python 3.7+, network access to zoom.us and api.zoom.us, and a local .env with Zoom Server-to-Server OAuth credentials.
description: Manage Zoom meetings, cloud recordings, and account users via a Server-to-Server OAuth REST script. Use this skill when the user wants to list, view, create, or delete a scheduled Zoom meeting; query cloud recordings for a user; or look up account users. Actions are restricted to a fixed list (list/get/create/delete meeting, get/list user, list recordings) — the script does not perform arbitrary Zoom API calls. create_meeting and delete_meeting require explicit user confirmation before execution. Requires a Zoom Server-to-Server OAuth app and a local .env with ACCOUNT_ID, CLIENT_ID, CLIENT_SECRET, USER_ID.
---

• Confidence: 84% confidence
• Finding: .env

Credential Access

High

• Category: Privilege Escalation

Content

name: zoom-meeting-admin
allowed-tools: Bash(python3:*) Bash(ls:*) Bash(cat:*) Read
compatibility: Requires Python 3.7+, network access to zoom.us and api.zoom.us, and a local .env with Zoom Server-to-Server OAuth credentials.
description: Manage Zoom meetings, cloud recordings, and account users via a Server-to-Server OAuth REST script. Use this skill when the user wants to list, view, create, or delete a scheduled Zoom meeting; query cloud recordings for a user; or look up account users. Actions are restricted to a fixed list (list/get/create/delete meeting, get/list user, list recordings) — the script does not perform arbitrary Zoom API calls. create_meeting and delete_meeting require explicit user confirmation before execution. Requires a Zoom Server-to-Server OAuth app and a local .env with ACCOUNT_ID, CLIENT_ID, CLIENT_SECRET, USER_ID.
---

# Zoom Server-to-Server OAuth REST API

• Confidence: 84% confidence
• Finding: .env

VirusTotal

65/65 vendors flagged this skill as clean.

Static analysis

No suspicious patterns detected.