pages_open_document

Open a Pages document from a file path.

SERVERAirMCP SOURCEairmcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/heznpc-airmcp/pages-open-document.md

WHAT IT DOES

What pages_open_document does on AirMCP

AI agents invoke pages_open_document to trigger actions in AirMCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

RISK

Why pages_open_document is rated High

Opening a document triggers an external application (Pages) to launch and load a file, which is an external operation beyond simple data retrieval. It causes a side effect in the OS environment (launching/activating an application). This goes beyond a pure Read operation, making Execute the most appropriate category.

From the tool's definition Open a Pages document from a file path

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs pages_open_document safely

PolicyLayer is an MCP gateway: it sits between your AI agents and AirMCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For pages_open_document, this is the rule to start with:

pages_open_document Rate-limited

pages_open_document stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "pages_open_document": {
      "limits": [
        {
          "counter": "pages_open_document_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect AirMCP, apply this rule, and every pages_open_document call is checked against it from then on.

FAQ

Questions about pages_open_document

What does the pages_open_document tool do? +

Open a Pages document from a file path. It is categorised as a Execute tool in the AirMCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on pages_open_document? +

Register the Air 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 AirMCP. Nothing to install.

What risk level is pages_open_document? +

pages_open_document is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

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 Air MCP server (airmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Air, and thousands of servers like it.

This server

All 279 Air tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →