Write data to a Numbers spreadsheet. Optionally specify sheet, table, and cell range.
AI agents use numbers.write to create or update resources in Orchard — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Orchard environment.
This tool creates or modifies data in a spreadsheet in a reversible manner. The write operation can be undone (via undo functionality or by overwriting), making it Write rather than Destructive. While it modifies user data, the blast radius is limited to a single spreadsheet document.
From the tool's definition Tool name 'numbers.write' and description explicitly states 'Write data to a Numbers spreadsheet' with control over sheet, table, and cell range parameters.
Documented attack patterns abuse exactly the kind of access numbers.write 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.write:
{
"version": "1",
"default": "deny",
"tools": {
"numbers.write": {
"limits": [
{
"counter": "numbers.write_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}numbers.write stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Write data to a Numbers spreadsheet. Optionally specify sheet, table, and cell range. It is categorised as a Write tool in the Orchard MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Orchard MCP server in PolicyLayer and add a rule for numbers.write: 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.write is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the numbers.write 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.write. 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.write 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.