azuresql-db-functions
Pass
Audited by Gen Agent Trust Hub on Sep 28, 2026
Risk Level: SAFEINDIRECT_PROMPT_INJECTION
Full Analysis
- [Credential Management]: The skill uses a
local.settings.jsontemplate for database connection strings and explicitly warns against committing this file to version control. This is a standard security practice to prevent the accidental exposure of sensitive configuration data.\n- [External Resource Access]: The instructions include pulling a container image from a preview Azure Container Registry (sqldbpreview-dpgaeqhmgphzd4bk.azurecr.io). This resource is part of the vendor's infrastructure for the technology being demonstrated.\n- [Data Ingestion Surface]: The skill describes an architecture that processes data from a database using SQL bindings.\n - Ingestion points: External data is ingested via
SqlInputandSqlTriggerbindings as described inSKILL.mdandreferences/functions-snippets.md.\n - Boundary markers: No specific prompt delimiters are shown in the transport-layer snippets.\n
- Capability inventory: The skill facilitates shell command execution for development tasks (
func,dotnet,docker) and the creation of network-facing API endpoints.\n - Sanitization: The use of typed models in the code snippets provides a layer of schema validation for processed data.\n- [Dependency and Tooling Configuration]: The guide uses standard commands for project initialization and dependency management, such as
dotnet add packageand configuring extension bundles inhost.json. These actions align with official documentation for extending Azure Functions.
Audit Metadata