T08 · Insecure Dependencies
- Location
SKILL.md:98- Finding
Unpinned Third-Party MCP Package Is Installed and Executed with an API Credential
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This is a coherent Local Falcon SEO skill, but users should review its MCP setup and install metadata because it can install/run external packages with an API key and trigger billable or account-changing actions.
Review before installing. Prefer a pinned, verified MCP package version, avoid storing the API key directly in broadly readable config files, confirm the marketplace package name before running npm install, and require explicit approval before scans, campaigns, or Falcon Guard changes that may spend credits or alter account state.
SKILL.md:98Unpinned Third-Party MCP Package Is Installed and Executed with an API Credential
marketplace.json:86Marketplace Metadata References a Different and Unverified npm Package
The trigger list includes very broad terms such as "local search," "local rankings," "AI Mode," and "Local Falcon," which can cause the skill to auto-invoke in many unrelated conversations. Over-broad auto-invocation expands the skill's authority and increases the chance that users are steered into this skill unexpectedly, including into setup flows involving external tools and API-key guidance.
The trigger phrase "review velocity" begins with the common built-in command word "review," creating a shadow-command conflict that could cause unintended invocation or interception when users attempt other review-related actions. In an auto-invoked skill, this kind of overlap is especially risky because it can hijack normal command routing and confuse users about which capability is responding.
The skill instructs users to place a long-lived API key in a local MCP configuration file via an environment variable, which creates session-persistence risk if that file is reused, exposed, logged, or committed accidentally. In skill context, this is more dangerous because the content explicitly walks the user through credential acquisition and durable storage, increasing the chance of sensitive secret retention beyond the immediate session.
**Step 2: Get a Local Falcon API key**
- Go to [localfalcon.com/api/credentials](https://www.localfalcon.com/api/credentials/)
- Create or copy your API key
- Requires an active Local Falcon subscription
**Step 3: Configure Claude Code**
The trigger list contains broad, generic phrases such as 'local seo', 'ai visibility', 'google business profile', and 'map pack' that are likely to match many ordinary user requests outside the user's explicit intent to invoke this specific skill. Overbroad invocation increases the chance the skill is auto-selected in unrelated contexts, which can cause prompt hijacking of routing, unintended exposure to the skill's instructions, or biased/commercial responses when a neutral answer was expected.
The workflow reference documents tools that can create campaigns, run scans that consume credits, and pause, resume, or remove monitored resources, but it does not prominently warn that these are state-changing and billable actions. In an agent setting, that omission increases the chance that a user or calling system will invoke destructive or costly operations without informed confirmation, leading to unauthorized changes or unexpected charges.
The markdown explicitly suggests the natural-language phrase "Check my Local Falcon account" as something that triggers tool use. While somewhat domain-specific, it is still presented as a free-form trigger without any constraints, negative examples, or clarification about when the skill should or should not activate, which increases the risk of unintended invocation in ordinary conversation about account status.
No suspicious patterns detected.