Delete a database

Request deletion of the database and its data. This requires the separate database-deletion permission. Nothing is deleted when the request is refused with HTTP 409: workload_busy while a restore or import runs on the database, project_deleting while its project is being deleted (that delete removes it).

Tool: deleteDatabase
Permission: databases:delete
Kind: Destructive

Clients are told this tool can remove, overwrite or interrupt resources, or grant access. Set your client to ask before it runs it.

Queued work: send an idempotencyKey and reuse the same value when retrying this exact call.

Arguments

Name	Type	Required	Limits
`projectId`	`string`	Yes	At least 1 character(s)
`databaseId`	`string`	Yes	At least 1 character(s)
`idempotencyKey`	`string`	Yes	At least 1 character(s)

Full input schema

{
  "type": "object",
  "properties": {
    "projectId": {
      "type": "string",
      "minLength": 1
    },
    "databaseId": {
      "type": "string",
      "minLength": 1
    },
    "idempotencyKey": {
      "type": "string",
      "minLength": 1,
      "maxLength": 200,
      "description": "Unique request key. Reuse this exact value when retrying the same operation."
    }
  },
  "required": [
    "projectId",
    "databaseId",
    "idempotencyKey"
  ],
  "additionalProperties": false
}

Example call

The params of a tools/call request. Replace the placeholder values with your own IDs.

{
  "name": "deleteDatabase",
  "arguments": {
    "projectId": "REPLACE_WITH_PROJECT_ID",
    "databaseId": "REPLACE_WITH_DATABASE_ID",
    "idempotencyKey": "REPLACE_WITH_IDEMPOTENCY_KEY"
  }
}

Result

The same data as the API operation, wrapped as {"untrusted_data": true, "source": "deleteDatabase", "note": "...", "data": ...} so the model treats project content as data, not instructions.