Undeclared Tool Scope
- Category
- MCP Least Privilege
- Confidence
- 70% confidence
- Finding
Without declared permissions the skill's intent is opaque and cannot be validated.
- Content
Security audit
Security checks for vulnerabilities and agentic risk
This skill is a straightforward Revid script-to-video integration that sends user-provided scripts to Revid as expected, with no hidden persistence or unrelated local access.
Install this only if you are comfortable sending the script text and your Revid API key to Revid's service for rendering. Avoid submitting confidential, regulated, or proprietary scripts unless your organization approves that third-party processing.
Without declared permissions the skill's intent is opaque and cannot be validated.
The skill instructs sending the user's full script to www.revid.ai but does not warn that the content leaves the local environment or may contain sensitive, proprietary, or personal information. Users may unknowingly disclose confidential scripts, internal documents, or regulated data to a third-party service, creating privacy, compliance, and data-governance risk.
The skill hardcodes an English (US) locale in the voice configuration, which can impose a specific language/locale by default. There is no accompanying instruction that users may choose another language or that this skill is intentionally limited to en-US for a documented reason.
The voice configuration hard-codes both a U.S. English voice ID and the language value "en-US". This imposes a specific language/locale choice without any indication of user opt-in or documentation that the skill is intentionally region-specific.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
PAYLOAD=$(cat "$PAYLOAD_FILE")
fi
PID=$(curl -fsS https://www.revid.ai/api/public/v3/render \
-H "Content-Type: application/json" -H "key: $REVID_API_KEY" \
-d "$PAYLOAD" | jq -r .pid)
echo "pid=$PID"
This manifest uses a generic workflow label, "script-to-video", without any surrounding constraints or negative examples clarifying when this skill should be invoked versus similar text-to-media tasks. In a manifest file, that kind of broad activation description can lead to unintended routing or ambiguous invocation behavior.