Skills azure-messaging Audit History
📦

Audit History

azure-messaging - 5 audits

Version comparison

Capability and finding changes across audited versions, newest first.

VersionDateResultReview itemsChange vs previous
v5 LatestJul 23, 2026, 06:53 PM 1 confirmed0No capability change
v4 Jul 8, 2026, 09:21 AM No confirmed findings0 Network access
v3 Jul 6, 2026, 07:14 PM No confirmed findings0No capability change
v2 Jun 30, 2026, 07:24 AM 1 confirmed0External commandsNetwork access
v1 Feb 22, 2026, 08:40 AM No confirmed findings0Baseline

Jul 23, 2026, 06:53 PM

All ten static findings are false positives caused by Markdown backticks around MCP tool names, operation names, and a path. No shell or Ruby execution is present in SKILL.md. The documented Azure MCP workflow can read cloud resource metadata and diagnostic logs, so users should apply least-privilege access.

2
Files scanned
64
Lines analyzed
2
Review items
0
False positives ignored

Confirmed security concerns (1)

Medium
Cloud Resource and Diagnostic Log Access
The skill directs Azure MCP tools to list messaging resources, check service health, and query diagnostic logs using the user's cloud permissions. These read operations may expose subscription topology and operational data.
The MCP tool table and diagnosis workflow explicitly describe resource listing, health checks, and KQL log queries. The documented operations are read-oriented but require authorized Azure access.
Audited by: codex

Jul 8, 2026, 09:21 AM

All static findings are false positives caused by Markdown inline-code backticks in SKILL.md. I found no prompt injection, data exfiltration intent, or unsafe command execution instructions in the reviewed content.

2
Files scanned
64
Lines analyzed
1
Review items
0
False positives ignored
Audited by: codex

Jul 6, 2026, 07:14 PM

All 20 static findings were adjudicated as false positives. The network hits are placeholder Azure endpoints or user-directed diagnostic checks, and the external-command hits are Markdown references to MCP tools. No prompt injection, malicious intent, or hidden data exfiltration behavior was found.

10
Files scanned
599
Lines analyzed
2
Review items
0
False positives ignored
Audited by: codex

Jun 30, 2026, 07:24 AM

Static analysis reported many command, network, browser storage, weak crypto, and reconnaissance patterns. Manual review found these are Markdown troubleshooting examples, Azure SDK identifiers, placeholder endpoints, and links to Microsoft or Azure documentation, not executable skill logic. No evidence found of malicious intent, prompt injection, credential exfiltration, or hidden code execution.

10
Files scanned
599
Lines analyzed
3
Review items
3
False positives ignored

Confirmed security concerns (1)

Low
MCP Tool References Require User-Authorized Azure Access
The skill recommends Azure MCP tools for service health, resource listing, diagnostic logs, and documentation search. This is a legitimate capability, but it requires user-authorized Azure access and should be treated as a low operational risk.
The tool names and workflow clearly indicate external Azure and documentation lookups. The risk is limited because the file only instructs use of named MCP tools and does not contain hidden exfiltration logic.
Static false positives ignored (3)

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
Markdown Command Examples Misclassified as Code Execution
The analyzer flagged many inline backticks and fenced examples as Ruby or shell execution. Manual review shows they are documentation snippets for SDK errors, logging settings, and connectivity tests, not executable files or invoked commands.
The referenced content is Markdown documentation and code samples. No file contains a runnable script, process spawn, eval call, or dynamic command execution path.
Low
External Links and Endpoint Placeholders Are Expected Documentation
Hardcoded URLs are references to GitHub, Microsoft Learn, Azure status, or placeholder Azure service endpoints. They document official troubleshooting sources and example endpoint formats rather than sending data to an external service.
URLs point to official Azure, Microsoft Learn, GitHub SDK documentation, or angle-bracket placeholders. No evidence shows data collection, callbacks, or unauthorized network requests.
Low
Browser Storage and Reconnaissance Patterns Are Troubleshooting Instructions
The browser storage finding is a JavaScript SDK logging example that sets local debug configuration. The reconnaissance findings are user-directed diagnostic commands such as DNS, socket, and network checks for connectivity troubleshooting.
The snippets are presented as troubleshooting guidance for the user to run in their own environment. They do not automate browser storage access or scan networks from the skill.

Risk Factors

⚙️ External commands (178)
references/sdk/azure-eventhubs-dotnet.md:3 references/sdk/azure-eventhubs-dotnet.md:9 references/sdk/azure-eventhubs-dotnet.md:10 references/sdk/azure-eventhubs-dotnet.md:11 references/sdk/azure-eventhubs-dotnet.md:12 references/sdk/azure-eventhubs-dotnet.md:13 references/sdk/azure-eventhubs-dotnet.md:17-23 references/sdk/azure-eventhubs-dotnet.md:23-27 references/sdk/azure-eventhubs-dotnet.md:27-31 references/sdk/azure-eventhubs-dotnet.md:31 references/sdk/azure-eventhubs-dotnet.md:31 references/sdk/azure-eventhubs-dotnet.md:31-35 references/sdk/azure-eventhubs-dotnet.md:35-36 references/sdk/azure-eventhubs-dotnet.md:36-40 references/sdk/azure-eventhubs-dotnet.md:40 references/sdk/azure-eventhubs-dotnet.md:40-42 references/sdk/azure-eventhubs-dotnet.md:42-61 references/sdk/azure-eventhubs-dotnet.md:61-66 references/sdk/azure-eventhubs-java.md:3 references/sdk/azure-eventhubs-java.md:11 references/sdk/azure-eventhubs-java.md:12 references/sdk/azure-eventhubs-java.md:13 references/sdk/azure-eventhubs-java.md:14 references/sdk/azure-eventhubs-java.md:18 references/sdk/azure-eventhubs-java.md:18 references/sdk/azure-eventhubs-java.md:20-22 references/sdk/azure-eventhubs-java.md:22-25 references/sdk/azure-eventhubs-java.md:25-27 references/sdk/azure-eventhubs-java.md:27-35 references/sdk/azure-eventhubs-java.md:35-39 references/sdk/azure-eventhubs-java.md:39-41 references/sdk/azure-eventhubs-java.md:41-58 references/sdk/azure-eventhubs-java.md:58-63 references/sdk/azure-eventhubs-java.md:63-67 references/sdk/azure-eventhubs-java.md:67 references/sdk/azure-eventhubs-js.md:3 references/sdk/azure-eventhubs-js.md:9 references/sdk/azure-eventhubs-js.md:10 references/sdk/azure-eventhubs-js.md:11 references/sdk/azure-eventhubs-js.md:11 references/sdk/azure-eventhubs-js.md:13 references/sdk/azure-eventhubs-js.md:13 references/sdk/azure-eventhubs-js.md:13 references/sdk/azure-eventhubs-js.md:13 references/sdk/azure-eventhubs-js.md:13 references/sdk/azure-eventhubs-js.md:13 references/sdk/azure-eventhubs-js.md:13 references/sdk/azure-eventhubs-js.md:13 references/sdk/azure-eventhubs-js.md:13 references/sdk/azure-eventhubs-js.md:17-26 references/sdk/azure-eventhubs-js.md:26-29 references/sdk/azure-eventhubs-js.md:29-31 references/sdk/azure-eventhubs-js.md:31-35 references/sdk/azure-eventhubs-js.md:35-40 references/sdk/azure-eventhubs-js.md:40-44 references/sdk/azure-eventhubs-js.md:44-46 references/sdk/azure-eventhubs-js.md:46-57 references/sdk/azure-eventhubs-js.md:57-62 references/sdk/azure-eventhubs-py.md:3 references/sdk/azure-eventhubs-py.md:9 references/sdk/azure-eventhubs-py.md:9 references/sdk/azure-eventhubs-py.md:9 references/sdk/azure-eventhubs-py.md:9 references/sdk/azure-eventhubs-py.md:10 references/sdk/azure-eventhubs-py.md:11 references/sdk/azure-eventhubs-py.md:12 references/sdk/azure-eventhubs-py.md:16-29 references/sdk/azure-eventhubs-py.md:29-33 references/sdk/azure-eventhubs-py.md:33-44 references/sdk/azure-eventhubs-py.md:44-48 references/sdk/azure-eventhubs-py.md:48 references/sdk/azure-eventhubs-py.md:48-52 references/sdk/azure-eventhubs-py.md:52 references/sdk/azure-eventhubs-py.md:52-56 references/sdk/azure-eventhubs-py.md:56 references/sdk/azure-eventhubs-py.md:56-58 references/sdk/azure-eventhubs-py.md:58-76 references/sdk/azure-servicebus-dotnet.md:3 references/sdk/azure-servicebus-dotnet.md:9 references/sdk/azure-servicebus-dotnet.md:10 references/sdk/azure-servicebus-dotnet.md:11 references/sdk/azure-servicebus-dotnet.md:12 references/sdk/azure-servicebus-dotnet.md:13 references/sdk/azure-servicebus-dotnet.md:14 references/sdk/azure-servicebus-dotnet.md:15 references/sdk/azure-servicebus-dotnet.md:19-25 references/sdk/azure-servicebus-dotnet.md:25-29 references/sdk/azure-servicebus-dotnet.md:29 references/sdk/azure-servicebus-dotnet.md:29 references/sdk/azure-servicebus-dotnet.md:29-32 references/sdk/azure-servicebus-dotnet.md:32-34 references/sdk/azure-servicebus-dotnet.md:34 references/sdk/azure-servicebus-dotnet.md:34-35 references/sdk/azure-servicebus-java.md:3 references/sdk/azure-servicebus-java.md:9 references/sdk/azure-servicebus-java.md:10 references/sdk/azure-servicebus-java.md:11 references/sdk/azure-servicebus-java.md:17 references/sdk/azure-servicebus-java.md:19 references/sdk/azure-servicebus-java.md:22-25 references/sdk/azure-servicebus-java.md:25-26 references/sdk/azure-servicebus-java.md:26-30 references/sdk/azure-servicebus-java.md:30-36 references/sdk/azure-servicebus-java.md:36 references/sdk/azure-servicebus-java.md:36-41 references/sdk/azure-servicebus-java.md:41-43 references/sdk/azure-servicebus-java.md:43-49 references/sdk/azure-servicebus-java.md:49 references/sdk/azure-servicebus-java.md:49 references/sdk/azure-servicebus-js.md:3 references/sdk/azure-servicebus-js.md:9 references/sdk/azure-servicebus-js.md:10 references/sdk/azure-servicebus-js.md:11 references/sdk/azure-servicebus-js.md:12 references/sdk/azure-servicebus-js.md:13 references/sdk/azure-servicebus-js.md:14 references/sdk/azure-servicebus-js.md:16 references/sdk/azure-servicebus-js.md:16 references/sdk/azure-servicebus-js.md:16 references/sdk/azure-servicebus-js.md:16 references/sdk/azure-servicebus-js.md:16 references/sdk/azure-servicebus-js.md:16 references/sdk/azure-servicebus-js.md:20-29 references/sdk/azure-servicebus-js.md:29-32 references/sdk/azure-servicebus-js.md:32-34 references/sdk/azure-servicebus-js.md:34-38 references/sdk/azure-servicebus-js.md:38 references/sdk/azure-servicebus-js.md:38-40 references/sdk/azure-servicebus-js.md:40-43 references/sdk/azure-servicebus-js.md:43 references/sdk/azure-servicebus-js.md:43-44 references/sdk/azure-servicebus-py.md:3 references/sdk/azure-servicebus-py.md:9 references/sdk/azure-servicebus-py.md:10 references/sdk/azure-servicebus-py.md:10 references/sdk/azure-servicebus-py.md:11 references/sdk/azure-servicebus-py.md:11 references/sdk/azure-servicebus-py.md:12 references/sdk/azure-servicebus-py.md:13 references/sdk/azure-servicebus-py.md:13 references/sdk/azure-servicebus-py.md:14 references/sdk/azure-servicebus-py.md:15 references/sdk/azure-servicebus-py.md:19-31 references/sdk/azure-servicebus-py.md:31-35 references/sdk/azure-servicebus-py.md:35-44 references/sdk/azure-servicebus-py.md:44-48 references/sdk/azure-servicebus-py.md:48 references/sdk/azure-servicebus-py.md:48-49 references/sdk/azure-servicebus-py.md:49 references/sdk/azure-servicebus-py.md:49 references/sdk/azure-servicebus-py.md:49-50 references/sdk/azure-servicebus-py.md:50 references/service-troubleshooting.md:9 references/service-troubleshooting.md:9 references/service-troubleshooting.md:18-24 references/service-troubleshooting.md:24-31 references/service-troubleshooting.md:31 references/service-troubleshooting.md:31-32 references/service-troubleshooting.md:32-39 references/service-troubleshooting.md:39 references/service-troubleshooting.md:39-40 references/service-troubleshooting.md:40-41 references/service-troubleshooting.md:41-42 references/service-troubleshooting.md:42-56 references/service-troubleshooting.md:56 references/service-troubleshooting.md:56-60 SKILL.md:22 SKILL.md:22 SKILL.md:36 SKILL.md:37 SKILL.md:38 SKILL.md:38 SKILL.md:39 SKILL.md:39 SKILL.md:40 SKILL.md:45 SKILL.md:47 SKILL.md:63
🌐 Network access (36)
Audited by: codex

Feb 22, 2026, 08:40 AM

This is a Microsoft-official troubleshooting reference skill containing only documentation and example commands for debugging Azure Event Hubs and Service Bus SDK issues. All static findings are false positives: code fences (backticks) are markdown examples, URLs point to official Microsoft documentation, and diagnostic commands are standard troubleshooting tools. No executable code or malicious patterns detected.

10
Files scanned
599
Lines analyzed
0
Review items
0
False positives ignored
No confirmed security findings were recorded for this completed audit.
Audited by: claude