Azure Keyvault Certificates Rust
ReviewAudited by ClawScan on May 1, 2026.
Overview
This is a straightforward Azure Key Vault Certificates Rust reference, but its examples use Azure credentials and include operations that can change or delete vault certificates.
This skill appears benign and purpose-aligned as an instruction-only Rust SDK reference. Before using its examples, make sure they target the correct Azure Key Vault and account, avoid hardcoding real certificate passwords, and treat create, import, update, delete, and purge examples as privileged operations requiring explicit review.
Findings (2)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Running generated code based on these examples against the wrong vault could delete or permanently remove certificates and disrupt services that depend on them.
The skill documents Azure Key Vault certificate mutation and deletion operations. This is aligned with the stated purpose, but these snippets can affect live cloud certificate resources if copied into production code.
client.delete_certificate("certificate-name", None).await?; ... "Purge" — permanent deletionUse these snippets only with the intended vault, prefer test vaults while developing, verify soft-delete/recovery settings, and require explicit human review before delete or purge operations.
Code generated from this skill may operate using the user's local Azure developer identity and whatever Key Vault permissions that identity has.
The examples use Azure developer credentials and describe a role with full certificate CRUD authority. This is expected for Key Vault certificate management, but it is privileged access.
let credential = DeveloperToolsCredential::new(None)?; ... `Key Vault Certificates Officer` — full CRUD on certificates
Confirm the Azure tenant, subscription, vault URL, and identity before running code; grant the least-privileged role needed, such as Reader for read-only tasks and Certificates Officer only when full management is required.