Skills azure-aigateway Audit History
📦

Audit History

azure-aigateway - 6 audits

Version comparison

Capability and finding changes across audited versions, newest first.

VersionDateResultReview itemsChange vs previous
v6 LatestJul 23, 2026, 05:49 PM 2 confirmed1No capability change
v5 Jul 8, 2026, 08:22 AM No confirmed findings0Filesystem access
v4 Jul 6, 2026, 06:54 PM No confirmed findings0No capability change
v3 Jul 6, 2026, 06:54 PM No confirmed findings0No capability change
v2 Jun 30, 2026, 07:59 AM No confirmed findings0Env variables
v1 Feb 21, 2026, 08:39 AM No confirmed findings0Baseline

Jul 23, 2026, 05:49 PM

The audit reviewed 80 static findings; 79 are documentation-related false positives. One finding is confirmed because an example imports an OpenAPI specification from a mutable branch. Semantic review also found caller-controlled rate-limit keys and commands that expose subscription keys.

10
Files scanned
1,195
Lines analyzed
7
Review items
0
False positives ignored

Confirmed security concerns (2)

High
Caller-Controlled Rate-Limit Key
Examples use the unverified X-Agent-Id request header as an APIM rate-limit counter key. Callers can rotate values to evade limits.
Both examples directly trust a caller-supplied header without authentication or validation. Rotating that value creates a clear rate-limit bypass.
High
Subscription Keys Exposed to Agent Output
Commands retrieve APIM subscription keys and a primary tracing key as terminal output. Agent sessions and logs could retain these active secrets.
The commands explicitly request subscription key material, including primaryKey, and print it for subsequent use. This exposes credentials to the invoking agent context.
Capability review items (1)

These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.

Low
Hardcoded URL
--specification-url "https://raw.githubusercontent.com/Azure/azure-rest-api-specs/main/specification
The command imports an OpenAPI specification directly from GitHub's mutable main branch. Upstream changes could alter the imported APIM API without local review.

Risk Factors

⚙️ External commands (21)
🔑 Env variables (14)
🌐 Network access (21)
📁 Filesystem access (4)
Audited by: codex

Jul 8, 2026, 08:22 AM

All static findings were adjudicated as false positives from Markdown documentation, Azure CLI examples, Azure SDK snippets, and APIM policy examples. No prompt injection attempt, credential exfiltration, malware behavior, or covert network behavior was found in the reviewed skill files.

10
Files scanned
1,195
Lines analyzed
4
Review items
0
False positives ignored

Risk Factors

⚙️ External commands (21)
🔑 Env variables (14)
🌐 Network access (21)
📁 Filesystem access (4)
Audited by: codex

Jul 6, 2026, 06:54 PM

All static findings were adjudicated as false positives after reviewing the cited source context. The flagged content is Markdown formatting, Azure CLI examples, APIM policy snippets, documentation links, and defensive content safety terminology. No evidence found of malware, prompt injection, credential exfiltration, or unauthorized command execution.

5
Files scanned
871
Lines analyzed
3
Review items
4
False positives ignored
Static false positives ignored (4)

These static matches were dismissed by semantic review or matched schema-only tokens, so they are shown for transparency but do not drive the quality score.

Critical
Known jailbreak keywords
Filter harmful content and detect jailbreak attempts.
Force-confirmed blocker/critical static finding; AI dismissal overridden.
Critical
Known jailbreak keywords
<!-- Block severity 4+ content, detect jailbreaks -->
Force-confirmed blocker/critical static finding; AI dismissal overridden.
Critical
Known jailbreak keywords
| `shield-prompt` | true/false | Detect jailbreak attempts |
Force-confirmed blocker/critical static finding; AI dismissal overridden.
Critical
Known jailbreak keywords
| **Content safety** | Enable `shield-prompt` to detect jailbreak attempts |
Force-confirmed blocker/critical static finding; AI dismissal overridden.

Risk Factors

🔑 Env variables (1)
⚙️ External commands (79)
🌐 Network access (24)
Audited by: codex

Jul 6, 2026, 06:54 PM

All static findings were adjudicated as false positives after reviewing the cited source context. The flagged content is Markdown formatting, Azure CLI examples, APIM policy snippets, documentation links, and defensive content safety terminology. No evidence found of malware, prompt injection, credential exfiltration, or unauthorized command execution.

5
Files scanned
871
Lines analyzed
3
Review items
4
False positives ignored
Static false positives ignored (4)

These static matches were dismissed by semantic review or matched schema-only tokens, so they are shown for transparency but do not drive the quality score.

Critical
Known jailbreak keywords
Filter harmful content and detect jailbreak attempts.
Force-confirmed blocker/critical static finding; AI dismissal overridden.
Critical
Known jailbreak keywords
<!-- Block severity 4+ content, detect jailbreaks -->
Force-confirmed blocker/critical static finding; AI dismissal overridden.
Critical
Known jailbreak keywords
| `shield-prompt` | true/false | Detect jailbreak attempts |
Force-confirmed blocker/critical static finding; AI dismissal overridden.
Critical
Known jailbreak keywords
| **Content safety** | Enable `shield-prompt` to detect jailbreak attempts |
Force-confirmed blocker/critical static finding; AI dismissal overridden.

Risk Factors

🔑 Env variables (1)
⚙️ External commands (79)
🌐 Network access (24)
Audited by: codex

Jun 30, 2026, 07:59 AM

Static analysis flagged many command, network, weak-crypto, and jailbreak-keyword patterns, but review found they are documentation examples for Azure API Management, policy snippets, SDK notes, and content-safety configuration. No hidden execution path, data exfiltration behavior, malicious prompt injection, or credential harvesting was found. The residual risk is low because users may copy cloud provisioning commands that affect Azure resources and costs.

5
Files scanned
871
Lines analyzed
3
Review items
4
False positives ignored
Static false positives ignored (4)

These static matches were dismissed by semantic review or matched schema-only tokens, so they are shown for transparency but do not drive the quality score.

Low
Documented Azure CLI and curl examples require user care
The external command findings are false positives for hidden execution. They appear in fenced examples for Azure CLI, package installation, and endpoint testing. The low residual risk is that users may copy commands that create Azure resources, assign roles, or call APIM endpoints.
The commands are inside Markdown code fences and are presented as deployment instructions. No file contains code that automatically executes these commands.
Low
Public documentation and sample URLs are expected network references
The network findings are false positives for exfiltration. The URLs point to Microsoft Learn, Azure sample repositories, a public Azure REST API specification, and placeholder backend URLs used in import examples.
The reviewed URLs are documentation, sample, or placeholder references. I found no code that sends secrets or user data to an unauthorized endpoint.
Low
SDK environment access reads an Azure subscription identifier
The env_access finding is low risk. The Python SDK quick reference reads AZURE_SUBSCRIPTION_ID to construct an Azure management client, which is normal for Azure SDK usage and is not a secret by itself.
The environment variable is used only as a subscription identifier in a documented SDK client example. No network exfiltration or broad environment dumping was found.
Low
Jailbreak and weak-crypto keyword hits are documentation terms
The critical jailbreak keyword and weak-cryptography findings are false positives. The skill discusses detecting jailbreak attempts with Azure content safety and uses terms like SHA or parameter types in normal documentation contexts, not bypass instructions or insecure cryptographic implementation.
The suspicious terms are used to describe protective content-safety policies and skill routing metadata. No prompt injection request, jailbreak procedure, or cryptographic code path was found.

Detected Patterns

Cloud resource modification examples
Audited by: codex

Feb 21, 2026, 08:39 AM

This is an official Microsoft skill for configuring Azure API Management as an AI Gateway. All static findings are false positives: external_commands are legitimate Azure CLI commands for infrastructure deployment, network findings are Microsoft documentation URLs, and 'jailbreak' references describe a content safety security feature that detects/blocks jailbreak attempts, not a vulnerability.

5
Files scanned
871
Lines analyzed
2
Review items
0
False positives ignored

Risk Factors

⚙️ External commands (1)
🌐 Network access (1)
Audited by: claude