confirm_destructive_operation

Execute a destructive database or API operation after confirmation. Use this only after reviewing the risks with the user.

HOW IT WORKS:

This tool executes a previously rejected high-risk operation using its confirmation ID
The operation will be exactly the same as the one that generated the ID
No need to retype the query or api request params - the system remembers it

STEPS:

Explain the risks to the user and get their approval
Use this tool with the confirmation ID from the error message
The original query will be executed as-is

PARAMETERS:

operation_type: Type of operation ("api" or "database")
confirmation_id: The ID provided in the error message (required)
user_confirmation: Set to true to confirm execution (default: false)

NOTE: Confirmation IDs expire after 5 minutes for security

Input Schema

Name	Required	Description	Default
`confirmation_id`	Yes
`operation_type`	Yes
`user_confirmation`	No

Input Schema (JSON Schema)

{
  "properties": {
    "confirmation_id": {
      "title": "Confirmation Id",
      "type": "string"
    },
    "operation_type": {
      "enum": [
        "api",
        "database"
      ],
      "title": "Operation Type",
      "type": "string"
    },
    "user_confirmation": {
      "default": false,
      "title": "User Confirmation",
      "type": "boolean"
    }
  },
  "required": [
    "operation_type",
    "confirmation_id"
  ],
  "title": "confirm_destructive_operationArguments",
  "type": "object"
}

Supabase MCP Server

confirm_destructive_operation

Input Schema

Input Schema (JSON Schema)

Other Tools