# start_export

Starts a read-only export of one Xero organisation's data. Costs $39 per organisation: when payment is outstanding the response is status 'awaiting_payment' with a Stripe checkoutUrl for the user to complete in a browser, and the export begins once that payment settles. This is not a status endpoint: it reports only the state at creation, and repeat calls return the existing export for that organisation rather than creating or charging for a second one. Export progress is reported by get_export_status, and newly created exports appear in list_exports. A typical export runs for hours, and pauses whenever it meets a Xero rate limit or Boxkite's egress budget — anything from under a minute to the next UTC day. get_export_status reports when it resumes.

Agent View of the PolicyLayer registry record for `start_export`. HTML page: https://policylayer.com/tools/com-getboxkite-xero-backup-export/start-export

## Facts

- Tool: `start_export`
- Server: Boxkite — Xero Backup & Export (`https://app.getboxkite.com/mcp`) — https://policylayer.com/tools/com-getboxkite-xero-backup-export.md
- Homepage: https://github.com/https://app.getboxkite.com/mcp
- Risk category: Financial (Critical risk)
- Registry record: grade D, identity unverified
- Server auth posture: open
- Server rate-limited: no
- Parameters: 1 (1 required)
- Recommended policy verdict: Approval-gated

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `organisationId` | string | yes | Organisation id from list_organisations |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "start_export",
    "arguments": {
      "organisationId": "<organisationId>"
    }
  }
}
```

## Why start_export is rated Critical

This tool triggers a financial transaction ($39 charge via Stripe) as part of its operation. Even though the data export itself is read-only, the act of initiating an export commits a financial obligation. Financial is the most severe applicable category per the rules.

From the tool's own definition: "Costs $39 per organisation: when payment is outstanding the response is status 'awaiting_payment' with a Stripe checkoutUrl for the user to complete in a browser, and the export begins once that payment settles."

## Use case

AI agents use start_export to commit financial operations through Boxkite — Xero Backup & Export, usually the final step of a payment, billing, or trading workflow. A call moves real money.

## Recommended policy (PolicyLayer)

Verdict: **Approval-gated**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Boxkite — Xero Backup & Export:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "start_export": {
      "deny_if": [
        {
          "conditions": [],
          "on_deny": "Requires human approval."
        }
      ]
    }
  }
}
```

## Other tools on Boxkite — Xero Backup & Export (6)

- `get_download_url` — Read — https://policylayer.com/tools/com-getboxkite-xero-backup-export/get-download-url.md
- `get_export_manifest` — Read — https://policylayer.com/tools/com-getboxkite-xero-backup-export/get-export-manifest.md
- `get_export_mapping` — Read — https://policylayer.com/tools/com-getboxkite-xero-backup-export/get-export-mapping.md
- `get_export_status` — Read — https://policylayer.com/tools/com-getboxkite-xero-backup-export/get-export-status.md
- `list_exports` — Read — https://policylayer.com/tools/com-getboxkite-xero-backup-export/list-exports.md
- `list_organisations` — Read — https://policylayer.com/tools/com-getboxkite-xero-backup-export/list-organisations.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=com-getboxkite-xero-backup-export · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-getboxkite-xero-backup-export