Create a backup schedule

Configure a WordPress or supported database backup using the permitted storage destination. Database backups require databaseId. Retention follows the organisation's plan.

Tool: createBackupPolicy
Permission: backups:write
Kind: Makes changes

Arguments

Name	Type	Required	Limits
`type`	`"database" \| "wordpress"`	Yes	See schema
`databaseId`	`string`	No	At least 1 character(s)
`schedule`	`string`	Yes	At least 1 character(s)
`prefix`	`string`	No	See schema
`destinationId`	`string`	No	At least 1 character(s)
`projectId`	`string`	Yes	At least 1 character(s)

Full input schema

{
  "type": "object",
  "properties": {
    "type": {
      "type": "string",
      "enum": [
        "database",
        "wordpress"
      ]
    },
    "databaseId": {
      "type": "string",
      "minLength": 1
    },
    "schedule": {
      "type": "string",
      "minLength": 1
    },
    "prefix": {
      "type": "string"
    },
    "destinationId": {
      "type": "string",
      "minLength": 1
    },
    "projectId": {
      "type": "string",
      "minLength": 1
    }
  },
  "required": [
    "projectId",
    "type",
    "schedule"
  ],
  "additionalProperties": false
}

Example call

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

{
  "name": "createBackupPolicy",
  "arguments": {
    "projectId": "REPLACE_WITH_PROJECT_ID",
    "type": "database",
    "schedule": "0 2 * * *",
    "databaseId": "REPLACE_WITH_DATABASE_ID"
  }
}

Result

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