Critical Risk →

pages_delete_text

Delete a paragraph by index (preserves formatting on other paragraphs)

How to control pages_delete_text ↓

What pages_delete_text does on Iwork

AI agents call pages_delete_text to permanently remove resources in Iwork — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why pages_delete_text needs a policy

This tool irreversibly deletes document content (paragraphs in a Pages document). While the deletion is scoped to a specific paragraph and formatting is preserved elsewhere, the action cannot be undone by the tool itself and represents loss of data. This is a Destructive operation, more severe than Write (which is reversible).

From the tool's definition Tool name is 'pages_delete_text' and description states 'Delete a paragraph by index' — uses the verb 'Delete' which indicates irreversible removal of content.

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

How to control pages_delete_text

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

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "pages_delete_text"
  ]
}

pages_delete_text disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

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

Free to start. No card required.

Related tools and policies

Go deeper

Questions about pages_delete_text

What does the pages_delete_text tool do? +

Delete a paragraph by index (preserves formatting on other paragraphs). It is categorised as a Destructive tool in the Iwork MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on pages_delete_text? +

Register the Iwork MCP server in PolicyLayer and add a rule for pages_delete_text: 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_delete_text? +

pages_delete_text is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit pages_delete_text? +

Yes. Add a rate_limit block to the pages_delete_text 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_delete_text completely? +

Set action: deny in the PolicyLayer policy for pages_delete_text. 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_delete_text? +

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

Free to start. No card required.

114 Iwork tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.