delete_subscription
A destructive tool on the Supabase MCP Server - Self-Hosted Edition MCP server.
This record as markdown: /tools/abdqum-supabase-mcp-selfhosted/delete-subscription.md
What delete_subscription does on Supabase MCP Server - Self-Hosted Edition
AI agents call delete_subscription to permanently remove resources in Supabase MCP Server - Self-Hosted Edition, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete_subscription is rated Critical
The 'delete' prefix categorizes this as Destructive rather than Write, as subscriptions typically cannot be easily recreated with identical state and history. In Supabase's real-time subscription context, deletion is an irreversible operation. Severity is high because unintended deletion of subscriptions could disrupt application real-time features and require manual recovery.
From the tool's definition Tool name is 'delete_subscription' which uses the verb 'delete', a destructive action. No description provided, but the name strongly indicates irreversible removal of a subscription record.
Attacks that exploit this kind of access
The rule that runs delete_subscription 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 delete_subscription, this is the rule to start with:
delete_subscription is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Supabase MCP Server - Self-Hosted Edition, apply this rule, and every delete_subscription call is checked against it from then on.
Questions about delete_subscription
delete_subscription is a destructive tool on the Supabase MCP Server - Self-Hosted Edition MCP server. It is categorised as a Destructive tool in the Supabase MCP Server - Self-Hosted Edition MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Supabase MCP Server - Self-Hosted Edition MCP server in PolicyLayer and add a rule for delete_subscription: 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 - Self-Hosted Edition. Nothing to install.
delete_subscription 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_subscription 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_subscription. 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_subscription is provided by the Supabase MCP Server - Self-Hosted Edition MCP server (abdqum/supabase-mcp-selfhosted). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Supabase MCP Server - Self-Hosted Edition, and thousands of servers like it.
This server
Across the catalogue