Add a new sheet to a Numbers spreadsheet.
AI agents use numbers.add_sheet 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 a new sheet within an existing Numbers spreadsheet, which is a reversible write operation. The user can delete the sheet afterwards. It does not execute arbitrary code, delete data irreversibly, or move financial resources. Severity is medium because unintended sheet additions could clutter spreadsheets or consume storage, but the impact is limited and easily remedied.
From the tool's definition Tool name 'add_sheet' and description 'Add a new sheet to a Numbers spreadsheet' indicate creation of new data structure within a spreadsheet document.
Documented attack patterns abuse exactly the kind of access numbers.add_sheet 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.add_sheet:
{
"version": "1",
"default": "deny",
"tools": {
"numbers.add_sheet": {
"limits": [
{
"counter": "numbers.add_sheet_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}numbers.add_sheet 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.
Add a new sheet to a Numbers spreadsheet. 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.add_sheet: 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.add_sheet 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.add_sheet 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.add_sheet. 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.add_sheet 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.