skills
amplitude/mcp-marketplace/plugins/amplitude/skills
- Type
- Skill
- Scanned
- Nov 13, 2026
- Version
- 658f88b994d8
- Files read
- 38
This plugin provides AI agent skills for querying Amplitude analytics, reviewing experiments and session replays, managing tracking plans, and adding event tracking to code. The biggest risk comes from running its instrumentation skills on untrusted pull requests or repositories, where crafted file names or instructions inside .amplitude/instrumentation-agent-context.md could trick the agent into running unintended shell commands, reading files outside the repository, or proposing unsafe tracking code.
What it can reach
- Network
- Reads and modifies Amplitude data through the Amplitude MCP server—including charts, dashboards, experiments, flags, cohorts, user profiles, session replays, customer feedback, AI session transcripts, guides, surveys, AI context, and tracking plans—and fetches pull request details from GitHub via the gh CLI.
- Files
- Reads source code, git history, and .amplitude configuration files in local repositories, and writes .amplitude/instrumentation-agent.yaml or tracking code changes when confirmed by the user.
- Shell commands
- Runs git and gh CLI commands to inspect branches, commits, and pull request diffs, and runs repository client-generation, build, and type-check commands during requested code cleanups.
- Secrets
- Scans repository initialization code for Amplitude API keys and environment variable references when bootstrapping project mappings, and relies on the user's configured Amplitude MCP and GitHub CLI credentials.
Findings
-
MediumUnquoted pull request file paths in git diff command template
plugins/amplitude/skills/diff-intake/SKILL.md:53
When a user asks to review or instrument a GitHub pull request, diff-intake fetches changed file paths from the PR via gh pr view and instructs the agent to pass those paths directly into an unquoted git diff shell command. Because Git permits characters such as $(), backticks, and semicolons in file names, a stranger who opens a pull request with a crafted file name (especially alongside prompt injection in the PR description read by gh pr view) could trick the agent into executing unintended shell commands on the user's machine.
Fix: Instruct the agent to pass file paths without shell expansion—for example, piping null-delimited paths into git diff --pathspec-from-file=- --pathspec-file-nul or strictly single-quoting each path—and treat PR titles, descriptions, and file names as untrusted data.
-
MediumRepository context file overrides skill rules and follows unchecked file references
plugins/amplitude/skills/discover-analytics-patterns/SKILL.md:26
When add-analytics-instrumentation or discover-analytics-patterns runs on a cloned repository or checked-out pull request branch, this skill reads .amplitude/instrumentation-agent-context.md and any files it references, treating its contents as directives that override the rest of the skill. Unlike instrument-events/SKILL.md—which explicitly warns the agent not to let that file override skill or safety rules—this skill omits that guardrail, does not prevent .. references from reading files outside the repository root, and lets the file dictate custom SDK or wrapper code patterns that get carried into the generated instrumentation plan.
Fix: Add the same safety boundary used in instrument-events/SKILL.md so the context file cannot override skill or safety rules, restrict referenced files to resolved paths strictly inside the repository root, and verify any declared SDK/wrapper patterns against existing repository code.
