azure-communication-callautomation-java

SAFE max severity MEDIUMSkillSpector Caution 0 registry microsoft last scanned 1 scan

Verdict safe, but 1 finding (1 medium), mainly data exfiltration. Most recent scan 2026-02-05.

This Azure Communication Services Call Automation skill is primarily a documentation/tutorial skill providing Java SDK examples. It contains no executable scripts and poses minimal direct security risk. The main concerns are: (1) missing metadata fields (license, compatibility, allowed-tools) which are informational/low severity issues, (2) code examples that demonstrate credential handling patterns without sufficient security warnings, and (3) a missing referenced file. The skill does not contain prompt injection attempts, data exfiltration code, command injection, or other high-severity threats. The credential handling examples warrant a MEDIUM severity finding as they could lead users to hardcode secrets if not properly warned. Overall, this is a relatively safe documentation skill that would benefit from improved metadata and security guidance in the examples.

Scanner's overall assessment (LLM analyzer)
Findings1
Critical0
High0
Medium1
Low0
Analyzersstatic behavioral llm trigger meta

Second scanner: NVIDIA SkillSpector

VerdictCaution 0
Score0 / 100
Issues0
Version2.12.0 (static)

SkillSpector found no issues but could not fully inspect the package, usually because SKILL.md refers to a file that is not present, so it fails closed to CAUTION instead of SAFE. Read it as "not fully checked", not as a finding. How the two scanners compare across the whole corpus: Two scanners, one corpus.

What this skill does

Build call automation workflows with Azure Communication Services Call Automation Java SDK. Use when implementing IVR systems, call routing, call recording, DTMF recognition, text-to-speech, or AI-powered call flows.

Package
3 files, 32 KB
SKILL.md
618 words, 12+ sections
Code
None. Instructions only.

SKILL.md covers: Azure Communication Call Automation (Java) · Installation · Client Creation · Key Concepts · Create Outbound Call · Answer Incoming Call · Play Audio (Text-to-Speech) · Recognize DTMF Input · Recognize Speech · Call Recording · Add Participant to Call · Transfer Call

Findings

MEDIUM Hardcoded Credentials in Code Examples Data Exfiltrationllm

The instruction body contains code examples with placeholder connection strings and endpoints that users might accidentally use with real credentials. While these are examples, they demonstrate patterns where sensitive credentials could be hardcoded directly in code.

SKILL.md

CallAutomationClient client = new CallAutomationClientBuilder()
    .connectionString("<connection-string>")
    .buildClient();
Remediation: Add explicit warnings in the instructions about never hardcoding real credentials. Recommend using environment variables or Azure Key Vault for credential management. Include example: System.getenv("AZURE_CONNECTION_STRING")

What is in the package

FileKindSize
SKILL.mddoc8.2 KB
references/acceptance-criteria.mddoc7.6 KB
references/examples.mddoc16 KB

External hosts referenced

your-app.com storage.blob.core.windows.net cognitive-services.cognitiveservices.azure.com github.com your-cognitive-services.cognitiveservices.azure.com

Hostnames that appear in the skill's files. Referencing a host is not a finding; compare against the findings above and the skill's stated purpose.

Environment variables referenced

AZURE_COMMUNICATION_CONNECTION_STRING AZURE_COMMUNICATION_ENDPOINT

Package contents recorded 2026-10-22 at commit cfbcbbdc679c. The scan above ran against the version current at scan time; the two can differ if the skill has since been updated.

What we checked

What we did not check

Sources

Related skills