List findings from the last audit of a project, optionally filtered by severity. Use after audit_project to inspect specific issues.
AI agents call list_findings to retrieve information from Supabase Security without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays security audit findings without modifying any state. It is purely informational. However, the sensitivity is elevated to 'medium' because the findings may contain details about security misconfigurations in a live Supabase project (database credentials, authentication gaps, public exposure risks, etc.), which could be valuable to an attacker if an agent is compromised or logs are…
From the tool's definition Tool description states it 'List findings from the last audit' — a retrieval operation with no side effects.
Attacks that exploit this kind of access
List findings from the last audit of a project, optionally filtered by severity. Use after audit_project to inspect specific issues. It is categorised as a Read tool in the Supabase Security MCP Server, which means it retrieves data without modifying state.
Register the Supabase Security MCP server in PolicyLayer and add a rule for list_findings: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Supabase Security. Nothing to install.
list_findings is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_findings rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for list_findings. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
list_findings is provided by the Supabase Security MCP server (perufitlife/supabase-security-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →