list_exports
List one-off exports (newest first), optionally for one organisation. Use this to find an export after payment and to poll its status until it is 'ready'. Side-effect free: it never starts a new export or charges anything. Each entry carries progress, parkedUntil and pollAfterSeconds.
This record as markdown: /tools/com-getboxkite-xero-backup-export/list-exports.md
What list_exports does on Boxkite — Xero Backup & Export
AI agents call list_exports to retrieve information from Boxkite — Xero Backup & Export without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
organisationId | string | — |
Parameters from the server's own tool schema.
Why list_exports is rated Low
This tool retrieves status information about existing exports. It performs a straightforward data query operation with no side effects, no modification capabilities, and explicitly no financial impact. The highest risk is information disclosure of export metadata, which is low severity in a read-only backup context.
From the tool's definition Tool description explicitly states 'Side-effect free: it never starts a new export or charges anything' and the operation is to 'List one-off exports'. The tool retrieves and queries existing export data without modification or external action.
Attacks that exploit this kind of access
The rule that runs list_exports safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Boxkite — Xero Backup & Export, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_exports, this is the rule to start with:
list_exports is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Boxkite — Xero Backup & Export, apply this rule, and every list_exports call is checked against it from then on.
Questions about list_exports
List one-off exports (newest first), optionally for one organisation. Use this to find an export after payment and to poll its status until it is 'ready'. Side-effect free: it never starts a new export or charges anything. Each entry carries progress, parkedUntil and pollAfterSeconds. It is categorised as a Read tool in the Boxkite — Xero Backup & Export MCP Server, which means it retrieves data without modifying state.
list_exports accepts 1 parameter: organisationId. The full parameter table on this page comes from the server's own tool schema.
Register the Boxkite — Xero Backup & Export MCP server in PolicyLayer and add a rule for list_exports: 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 Boxkite — Xero Backup & Export. Nothing to install.
list_exports is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_exports 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 list_exports. 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.
list_exports is provided by the Boxkite — Xero Backup & Export MCP server (https://app.getboxkite.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Boxkite — Xero Backup & Export, and thousands of servers like it.
This server
Across the catalogue