pages_open_document

THE RISK

Low Risk

Why pages_open_document needs a policy

Opening a file from disk is a read operation — it retrieves and loads the document into memory without creating, modifying, or deleting any data. No destructive or write side effects are implied.

From the tool's definition Open a .pages file from disk

Documented attack patterns abuse exactly the kind of access pages_open_document gives an agent:

POLICY

How to control pages_open_document

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 pages_open_document:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "pages_open_document": {}
  }
}

pages_open_document is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Iwork — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Iwork tools

Destructive keynote_delete_slide Delete a slide from the presentation Destructive numbers_clear_cells Clear the contents of a cell or range Destructive numbers_delete_column Delete one or more columns from a table Destructive numbers_delete_row Delete one or more rows from a table Destructive numbers_delete_sheet Delete a sheet from a Numbers document Destructive numbers_delete_table Delete a table from a sheet Destructive pages_delete_text Delete a paragraph by index (preserves formatting on other paragraphs) Destructive keynote_close_presentation Close a Keynote presentation

All 114 Iwork tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about pages_open_document

What does the pages_open_document tool do? +

Open a .pages file from disk. It is categorised as a Read tool in the Iwork MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on pages_open_document? +

Register the Iwork MCP server in PolicyLayer and add a rule for pages_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.

What risk level is pages_open_document? +

pages_open_document is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit pages_open_document? +

Yes. Add a rate_limit block to the pages_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.

How do I block pages_open_document completely? +

Set action: deny in the PolicyLayer policy for pages_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.

What MCP server provides pages_open_document? +

pages_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.

Enforce policy on every Iwork tool call.

Start from Iwork, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →