Security audit
Security checks for vulnerabilities and agentic risk
This skill is a coherent PoYo music-generation helper, but users should only submit trusted JSON payload files and approved callback URLs.
Install only if you intend to use PoYo's API. Keep POYO_API_KEY server-side, avoid sending private lyrics or sensitive files, review payload JSON before submission, and use callback URLs only on trusted HTTPS endpoints you control.
scripts/submit_generate_music.sh:9Unvalidated Arbitrary File Upload to a Third-Party API
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
Content-Type: application/json
Get API keys from <https://poyo.ai/dashboard/api-key>.
Recommended skill env var:
The skill advertises shell-based execution paths via curl and a submission script, but it does not declare any explicit tool restrictions such as allowed-tools or permissions. This weakens least-privilege controls and can let an agent invoke shell capabilities more broadly than necessary, increasing the chance of unintended command execution or unsafe handling of secrets like POYO_API_KEY.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
Use simple mode when the user wants a fast first test with a compact prompt.
curl --fail-with-body --request POST \
--url "https://api.poyo.ai/api/generate/submit" \
--header "Authorization: Bearer YOUR_API_KEY" \
--header "Content-Type: application/json" \
This example includes a user-controlled callback_url that can cause PoYo to send asynchronous job data to an arbitrary external endpoint. In a skill context, if this parameter is passed through without validation, it can enable data exfiltration, leaking task metadata/results to attacker-controlled infrastructure, or SSRF-style abuse against internal webhook receivers.
curl --fail-with-body --request POST \
--url "https://api.poyo.ai/api/generate/submit" \
--header "Authorization: Bearer YOUR_API_KEY" \
--header "Content-Type: application/json" \
--data '{
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
payload_file="$1"
curl --fail-with-body --request POST \
--url "https://api.poyo.ai/api/generate/submit" \
--header "Authorization: Bearer ${POYO_API_KEY}" \
--header "Content-Type: application/json" \
The script performs a network POST request and uploads the contents of the provided payload file to an external service. While this may be part of the script's function, there is no visible disclosure, prompt, or explanatory comment in the file warning that local file contents will be transmitted off-system.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
payload_file="$1"
curl --fail-with-body --request POST \
--url "https://api.poyo.ai/api/generate/submit" \
--header "Authorization: Bearer ${POYO_API_KEY}" \
--header "Content-Type: application/json" \
--data @"${payload_file}"
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
payload_file="$1"
curl --fail-with-body --request POST \
--url "https://api.poyo.ai/api/generate/submit" \
--header "Authorization: Bearer ${POYO_API_KEY}" \
--header "Content-Type: application/json" \
--data @"${payload_file}"
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
payload_file="$1"
curl --fail-with-body --request POST \
--url "https://api.poyo.ai/api/generate/submit" \
--header "Authorization: Bearer ${POYO_API_KEY}" \
--header "Content-Type: application/json" \
--data @"${payload_file}"
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
payload_file="$1"
curl --fail-with-body --request POST \
--url "https://api.poyo.ai/api/generate/submit" \
--header "Authorization: Bearer ${POYO_API_KEY}" \
--header "Content-Type: application/json" \
--data @"${payload_file}"
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
payload_file="$1"
curl --fail-with-body --request POST \
--url "https://api.poyo.ai/api/generate/submit" \
--header "Authorization: Bearer ${POYO_API_KEY}" \
--header "Content-Type: application/json" \
--data @"${payload_file}"
The 'Use When' section lists broad concepts like 'song ideas' and 'background tracks' as triggers, which can overlap with ordinary conversation and may cause unintended invocation. The file does not provide negative examples or explicit boundaries for when the skill should not activate.