Airlock RLS
NPM · AIRLOCK-RLS-MCP
Scan a deployed site for an exposed Supabase service_role key and audit Row Level Security.
Available components
Last scanned (29 minutes ago)
Scores higher than 40% of npm servers
Category Security
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security99
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 7 of 23 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 3 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 399 tokens (~199/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 16 Oct 26 +1
No change was recorded against any check on this day. Supply Chain Security went from 98 to 99.
- 14 Oct 26 70
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 17 Oct 2026 · Analysed npm/airlock-rls-mcp@0.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 23 packages
| Packages resolved | 23 |
|---|---|
| Stale | 7 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
audit_supabase_rls ~207
Audit a Supabase/Postgres database's Row Level Security. Fails when a table has RLS disabled, when a policy is permissive (USING (true) / WITH CHECK (true) or anything that reduces to always-true), when an anon or authenticated policy does not scope rows to the caller (tenant leak), and on exposed materialized views. Reads ONLY catalog metadata (pg_tables, pg_policies, grants, functions, views) — never your row data. A read-only connection string is enough.
| Name | Type | Req | Description |
|---|---|---|---|
| allow | array | – | Policy names that are intentionally permissive (e.g. a public status page). Prefer the qualified form "table.policy". |
| db_url | string | yes | Postgres connection string for the project to audit (e.g. postgresql://... — get it from `supabase status` locally or your project's connection settings). A read-only role is enough. |
| schema | string | – | Schema to audit (default: public). |
No output schema declared.
No examples provided.
scan_site_for_exposed_key ~192
Scan a DEPLOYED website's HTML and JavaScript bundles for an exposed Supabase service_role key (a service_role JWT or an sb_secret_... key). Needs only the public URL — no database, no credentials. A found key is a critical leak: it bypasses ALL Row Level Security, giving anyone who reads it full read/write to the database. Use this right after deploying a Supabase app, or whenever an AI-generated app might have bundled a secret into the frontend. Never prints the full key.
| Name | Type | Req | Description |
|---|---|---|---|
| max_scripts | integer | – | How many JS bundles to read (default 50). If the site has more, the result says how many went unscanned instead of implying it looked at all. |
| site_url | string | yes | Public https URL of the deployed site to scan (e.g. https://myapp.com). Only public http(s) hosts are allowed. |
No output schema declared.
No examples provided.
How do I install the Airlock RLS MCP server?
Airlock RLS runs locally as an npm package, launched with npx -y airlock-rls-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · airlock-rls-mcp
claude mcp add mateuszingano-airlock-rls-mcp -- npx -y airlock-rls-mcp
What is the Airlock RLS MCP server?
Airlock RLS is an MCP server listed in the public MCP registry as io.github.mateuszingano/airlock-rls-mcp. Scan a deployed site for an exposed Supabase service_role key and audit Row Level Security. This page covers its npm package (airlock-rls-mcp).
Is the Airlock RLS MCP server safe to use?
Airlock RLS scores 71 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 17 October 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Airlock RLS MCP server expose?
Airlock RLS exposes 2 tools: scan_site_for_exposed_key, audit_supabase_rls. Their descriptions and schemas cost roughly 399 tokens of context every time the server is loaded.
Is the Airlock RLS MCP server still maintained?
Airlock RLS is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Airlock RLS MCP server under?
Airlock RLS declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.