Microsoft Azure Sql Database
v1.0.2Microsoft Azure SQL Database integration. Manage data, records, and automate workflows. Use when the user wants to interact with Microsoft Azure SQL Database...
⭐ 0· 55·0 current·0 all-time
byVlad Ursul@gora050
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description (Azure SQL DB integration) align with the instructions: all steps call the Membrane CLI to create connections, list actions, run actions, or proxy requests. No unrelated credentials, binaries, or surprising capabilities are requested.
Instruction Scope
Instructions are narrowly scoped to installing and using the Membrane CLI, performing login via browser, creating connections, listing actions, running actions, and proxying requests. One important behavioral note: the instructions route API requests and authentication through Membrane’s service (server-side), so request payloads and queries will be visible to Membrane — this is expected for a proxy-based integration but is a privacy/operational consideration.
Install Mechanism
Install is an npm global install or use of npx (both referenced). npm is a standard package mechanism; this is proportionate to a CLI-based integration. Users should verify the @membranehq/cli package source and integrity before installing global packages.
Credentials
The skill declares no required env vars, no config paths, and no credentials. Authentication is done via Membrane's login flow, which matches the stated guidance ('let Membrane handle credentials'). There are no requests for unrelated secrets.
Persistence & Privilege
Skill is instruction-only, has no install spec that writes files, does not request always:true, and is user-invocable. It does not request elevated or persistent platform privileges.
Assessment
This skill appears to be what it says: a Membrane-based integration for Azure SQL Database. Before installing or using it, consider: (1) you will install an npm CLI (@membranehq/cli) — verify the package and publisher; (2) authentication and proxied requests go through Membrane servers, so data and queries may be visible to that service — ensure this fits your privacy/compliance requirements; (3) prefer per-connection least-privilege credentials on the Azure side (limit DB permissions and lifetime of connections); and (4) in headless or automated environments, follow the documented headless auth flow carefully to avoid exposing codes in logs. If you need assurance, review the official Membrane CLI repository and their privacy/security docs before proceeding.Like a lobster shell, security has layers — review code before you run it.
latestvk972jrdwazf7vy6msa2vka5ftn842wcc
License
MIT-0
Free to use, modify, and redistribute. No attribution required.