Delete records from a Supabase table based on filter conditions
AI agents call delete_records to permanently remove resources in Supabase MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deletion of database records is irreversible and destructive. Even though filter conditions limit scope, an improperly constructed filter could delete unintended records. The capability to permanently remove data from a production database represents a high-severity risk if misused by an AI agent (e.g., due to prompt injection or logic error).
From the tool's definition Tool name is 'delete_records' and description states 'Delete records from a Supabase table based on filter conditions' — this irreversibly removes data.
Attacks that exploit this kind of access
Delete records from a Supabase table based on filter conditions. It is categorised as a Destructive tool in the Supabase MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Supabase MCP Server MCP server in PolicyLayer and add a rule for delete_records: 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 MCP Server. Nothing to install.
delete_records is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_records 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 delete_records. 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.
delete_records is provided by the Supabase MCP Server MCP server (ninad7007/supabase-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 →