Open a .numbers file from disk
AI agents call numbers_open_document to retrieve information from Iwork without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool opens an existing file for reading/access. It retrieves/loads a document but does not modify, delete, or create data. Opening a file is a read-level operation with minimal blast radius.
From the tool's definition Open a .numbers file from disk
Documented attack patterns abuse exactly the kind of access numbers_open_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_open_document:
{
"version": "1",
"default": "deny",
"tools": {
"numbers_open_document": {}
}
} numbers_open_document is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Open a .numbers file from disk. It is categorised as a Read tool in the Iwork MCP Server, which means it retrieves data without modifying state.
Register the Iwork MCP server in PolicyLayer and add a rule for numbers_open_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_open_document is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the numbers_open_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_open_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_open_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.