Export a Numbers spreadsheet to another format (CSV, PDF, or XLSX).
AI agents call numbers.export to retrieve information from Orchard without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Exporting data is fundamentally a read operation that retrieves spreadsheet contents and converts them to different file formats. It does not modify, delete, or execute code; it does not move money or trigger external operations with unpredictable side effects. The blast radius is low because it only retrieves data the user already has access to and outputs it in a different format.
From the tool's definition Tool name and description: 'Export a Numbers spreadsheet to another format (CSV, PDF, or XLSX)' — the operation retrieves/exports existing spreadsheet data without modifying the source document or executing code.
Documented attack patterns abuse exactly the kind of access numbers.export gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Orchard, and nothing reaches the server without passing your rules. This is the rule we recommend for numbers.export:
{
"version": "1",
"default": "deny",
"tools": {
"numbers.export": {}
}
}numbers.export is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Export a Numbers spreadsheet to another format (CSV, PDF, or XLSX). It is categorised as a Read tool in the Orchard MCP Server, which means it retrieves data without modifying state.
Register the Orchard MCP server in PolicyLayer and add a rule for numbers.export: 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 Orchard. Nothing to install.
numbers.export 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 numbers.export 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 numbers.export. 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.
numbers.export is provided by the Orchard MCP server (l22-io/orchard-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Orchard, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
65 Orchard tools catalogued and risk-classified — across an index of 43,000+ MCP servers.