analyze_rls_coverage

What analyze_rls_coverage does on Supabase MCP Server - Self-Hosted Edition

AI agents call analyze_rls_coverage to retrieve information from Supabase MCP Server - Self-Hosted Edition without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why analyze_rls_coverage is rated Low

RLS coverage analysis is a read-only auditing operation that examines existing security policies without altering data or executing external commands. The context of sibling tools (audit_security, check_health) supports this as a monitoring/inspection function. Empty description prevents higher confidence, but the semantic meaning of 'analyze' and 'coverage' strongly suggests introspection over mutation.

From the tool's definition Tool name 'analyze_rls_coverage' suggests analysis of Row-Level Security policy coverage; the suffix 'analyze' and 'coverage' imply inspection/audit rather than modification. Description is empty, reducing confidence.

The rule that runs analyze_rls_coverage safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Supabase MCP Server - Self-Hosted Edition, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For analyze_rls_coverage, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "analyze_rls_coverage": {}
  }
}

Questions about analyze_rls_coverage