Add a new sheet to a Numbers document. By default, deletes the empty
AI agents use numbers_add_sheet to create or update resources in Iwork — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Iwork environment.
Adding a sheet to a spreadsheet is a reversible modification that creates new content without permanently destroying data. This fits the Write category (creates or modifies data reversibly). While the truncated description hints at deletion of empty sheets, the named action is sheet addition. Confidence is reduced from 0.9 to 0.85 due to the incomplete description.
From the tool's definition Tool name 'numbers_add_sheet' and description indicate it 'Add a new sheet to a Numbers document.' This is a creation operation that modifies document structure by adding a new sheet.
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 Iwork, 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 document. By default, deletes the empty. It is categorised as a Write tool in the Iwork MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Iwork 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 Iwork. 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 Iwork MCP server (reichenbach/iwork_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Iwork, 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.
114 Iwork tools catalogued and risk-classified — across an index of 43,000+ MCP servers.