Trust Assessment
plex received a trust score of 51/100, placing it in the Caution category. This skill has some security considerations that users should review before deployment.
SkillShield's automated analysis identified 3 findings: 1 critical, 1 high, 1 medium, and 0 low severity. Key findings include Network egress to untrusted endpoints, Plex Token exposed in URL query parameters, Potential Command Injection via unsanitized search term.
The analysis covered 4 layers: Manifest Analysis, Static Code Analysis, Dependency Graph, LLM Behavioral Safety. All layers scored 70 or above, reflecting consistent security practices.
Last analyzed on February 13, 2026 (commit 13146e6a). SkillShield performs automated 4-layer security analysis on AI skills and MCP servers.
Layer Breakdown
Behavioral Risk Signals
Security Findings3
| Severity | Finding | Layer | Location | |
|---|---|---|---|---|
| CRITICAL | Network egress to untrusted endpoints HTTP request to raw IP address Review all outbound network calls. Remove connections to webhook collectors, paste sites, and raw IP addresses. Legitimate API calls should use well-known service domains. | Manifest | skills/dbhurley/plex/SKILL.md:9 | |
| HIGH | Potential Command Injection via unsanitized search term The `Search` command example uses a `SEARCH_TERM` placeholder directly within a `curl` command's URL query string. If the host LLM substitutes user-provided input into `SEARCH_TERM` without proper URL encoding and shell escaping, an attacker could inject arbitrary shell commands, leading to remote code execution. When constructing the `curl` command, ensure that any user-provided input for `SEARCH_TERM` is thoroughly URL-encoded and shell-escaped before insertion into the command string. For example, use a function that performs `urllib.parse.quote_plus` for the URL part and `shlex.quote` for the shell command part if the LLM is generating a shell command. | LLM | SKILL.md:30 | |
| MEDIUM | Plex Token exposed in URL query parameters The skill examples demonstrate using the `PLEX_TOKEN` directly in the URL query string (`?X-Plex-Token=$PLEX_TOKEN`). While this is a common pattern for the Plex API, it exposes the sensitive token in server access logs, proxy logs, and potentially browser history, making it vulnerable to passive logging and increasing the risk of compromise. If possible, use HTTP headers for authentication tokens instead of URL query parameters. If the Plex API only supports tokens in the URL, ensure that all systems handling these requests (proxies, web servers) are configured to redact or encrypt sensitive URL components in logs. | LLM | SKILL.md:20 |
Scan History
Embed Code
[](https://skillshield.io/report/8b6c0101994ac49c)
Powered by SkillShield