pages_close_document

Close an open Pages document, optionally saving changes.

SERVERIconnect SOURCEiconnect-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-heznpc-iconnect/pages-close-document.md

WHAT IT DOES

What pages_close_document does on Iconnect

AI agents use pages_close_document to create or update resources in Iconnect, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Iconnect environment.

RISK

Why pages_close_document is rated Medium

This tool modifies document state by either persisting or discarding changes. While closing without saving could be seen as destructive, the description explicitly indicates the save behavior is optional and user-controlled, making it primarily a write operation.

From the tool's definition 'Close an open Pages document, optionally saving changes' — the tool can modify (save) or discard changes to a document, making it a write operation that alters the state of user data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs pages_close_document safely

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

pages_close_document Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "pages_close_document": {
      "limits": [
        {
          "counter": "pages_close_document_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about pages_close_document

What does the pages_close_document tool do? +

Close an open Pages document, optionally saving changes. It is categorised as a Write tool in the Iconnect MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on pages_close_document? +

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

What risk level is pages_close_document? +

pages_close_document is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit pages_close_document? +

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

How do I block pages_close_document completely? +

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

What MCP server provides pages_close_document? +

pages_close_document is provided by the Iconnect MCP server (iconnect-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Iconnect, and thousands of servers like it.

This server

All 279 Iconnect tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →