AI agents call numbers.remove_sheet to permanently remove resources in Orchard — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Removing a sheet from a spreadsheet is a destructive action that cannot be easily undone. While users may have backups, the operation permanently deletes the sheet and any data it contained from the active spreadsheet. This is an irreversible data loss operation that justifies the Destructive category.
From the tool's definition Tool name is 'numbers.remove_sheet' and description states it will 'Remove a sheet from a Numbers spreadsheet' — this irreversibly deletes a sheet and its data from a spreadsheet file.
Documented attack patterns abuse exactly the kind of access numbers.remove_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.remove_sheet:
{
"version": "1",
"default": "deny",
"hide": [
"numbers.remove_sheet"
]
} numbers.remove_sheet disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Remove a sheet from a Numbers spreadsheet. It is categorised as a Destructive tool in the Orchard MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Orchard MCP server in PolicyLayer and add a rule for numbers.remove_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.remove_sheet is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the numbers.remove_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.remove_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.remove_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.