High Risk →

zoom_to_page

Zoom to fit page in view

How to control zoom_to_page ↓

AI agents invoke zoom_to_page to trigger actions in InDesign UXP MCP Server. 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.

High Risk

This tool triggers a UI/view action in Adobe InDesign — adjusting the zoom level to fit a page in the viewport. It doesn't read, write, or delete data, but it does execute an operation that changes the application's view state. It's low severity since it only affects the display, not any document content.

From the tool's definition Zoom to fit page in view

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

PolicyLayer is an MCP gateway — it sits between your AI agents and InDesign UXP MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for zoom_to_page:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "zoom_to_page": {
      "limits": [
        {
          "counter": "zoom_to_page_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

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

  1. Create a free account and register InDesign UXP MCP Server — 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.
RATE-LIMIT THIS TOOL →

Free to start. No card required.

Go deeper

What does the zoom_to_page tool do? +

Zoom to fit page in view. It is categorised as a Execute tool in the InDesign UXP MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on zoom_to_page? +

Register the InDesign UXP MCP Server MCP server in PolicyLayer and add a rule for zoom_to_page: 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 InDesign UXP MCP Server. Nothing to install.

What risk level is zoom_to_page? +

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

Can I rate-limit zoom_to_page? +

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

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

zoom_to_page is provided by the InDesign UXP MCP Server MCP server (theloniuser/indesign-uxp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every InDesign UXP MCP Server tool call.

Deterministic rules across all 135 InDesign UXP MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

135 InDesign UXP MCP Server tools catalogued and risk-classified — across an index of 42,500+ 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.