Close a Numbers document
AI agents use numbers_close_document 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.
Closing a document is a reversible state-change operation—the document file remains on disk and can be reopened. This falls under Write category (modify application state). The severity is low because closing a document is a safe, non-destructive action with minimal blast radius.
From the tool's definition The tool name 'numbers_close_document' and description 'Close a Numbers document' indicate a document lifecycle operation that does not retrieve data (Read), execute arbitrary code (Execute), permanently delete data (Destructive), or move money (Financial).
Documented attack patterns abuse exactly the kind of access numbers_close_document 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_close_document:
{
"version": "1",
"default": "deny",
"tools": {
"numbers_close_document": {
"limits": [
{
"counter": "numbers_close_document_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}numbers_close_document 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.
Close a Numbers document. 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_close_document: 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_close_document 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_close_document 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_close_document. 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_close_document 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.