get_export_status

SERVERBoxkite — Xero Backup & Export SOURCEhttps://app.getboxkite.com/mcp

Low RISK CLASS

Category Read

Parameters 11 required

Recommended Allowedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/com-getboxkite-xero-backup-export/get-export-status.md

WHAT IT DOES

What get_export_status does on Boxkite — Xero Backup & Export

AI agents call get_export_status 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
`exportId`	string	Yes

Parameters from the server's own tool schema.

RISK

Why get_export_status is rated Low

This tool only retrieves metadata about an export's current state and progress—it does not modify, delete, or execute operations on Xero data. It is a passive monitoring/status-checking function that queries the state of a previously initiated export. The read-only nature of the server and the absence of any mutating verbs (create, update, delete, execute) confirm the Read category.

From the tool's definition Tool description states it 'Reports the state of one export' and returns status information (status, progress metrics, timestamps, polling intervals).

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_export_status 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 get_export_status, this is the rule to start with:

get_export_status Allowed

get_export_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_export_status": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Boxkite — Xero Backup & Export, apply this rule, and every get_export_status call is checked against it from then on.

FAQ

Questions about get_export_status

What does the get_export_status tool do? +

Reports the state of one export: status (queued | running | ready | failed) and whether its download is available yet. Also returns progress {discovered, transferred, percent}; parkedUntil; and pollAfterSeconds, the interval after which this status is expected to have changed. A large export runs for hours, so pollAfterSeconds can be a long interval. parkedUntil is a timestamp, present whenever work on the organisation is paused and expected to resume. How long varies by cause and is not worth guessing at: hitting Xero's per-minute limit pauses for under a minute, approaching its daily quota pauses for about an hour, and exhausting the daily quota or Boxkite's own egress budget pauses until the next UTC day. Wait until the timestamp (or pollAfterSeconds, which already accounts for it) rather than describing a cause to the user. It is categorised as a Read tool in the Boxkite — Xero Backup & Export MCP Server, which means it retrieves data without modifying state.

What parameters does get_export_status accept? +

get_export_status accepts 1 parameter: exportId. Required: exportId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_export_status? +

Register the Boxkite — Xero Backup & Export MCP server in PolicyLayer and add a rule for get_export_status: 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.

What risk level is get_export_status? +

get_export_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_export_status? +

Yes. Add a rate_limit block to the get_export_status 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.

How do I block get_export_status completely? +

Set action: deny in the PolicyLayer policy for get_export_status. 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.

What MCP server provides get_export_status? +

get_export_status 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.

KEEP EXPLORING

More on Boxkite — Xero Backup & Export, and thousands of servers like it.

This server

All 7 Boxkite — Xero Backup & Export tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_file_snippet on ACE-MCP →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →