Low Risk

pages_get_body_text

Read all body text from a Pages document

How to control pages_get_body_text ↓

What pages_get_body_text does on Iwork

AI agents call pages_get_body_text 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.

Low Risk

Why pages_get_body_text needs a policy

This tool retrieves document content without modifying, deleting, or executing any operations. It performs a read-only query of existing data from a Pages document, fitting the Read category definition of retrieving or querying data with no side effects. The blast radius of misuse is minimal as it only accesses text content without ability to modify or delete.

From the tool's definition The tool description explicitly states 'Read all body text from a Pages document'

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

How to control pages_get_body_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_get_body_text:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "pages_get_body_text": {}
  }
}

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

  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.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about pages_get_body_text

What does the pages_get_body_text tool do? +

Read all body text from a Pages document. 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_get_body_text? +

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

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

Can I rate-limit pages_get_body_text? +

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

Set action: deny in the PolicyLayer policy for pages_get_body_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_get_body_text? +

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