AI agents invoke navigate_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.
Navigation actions are Execute category because they trigger operations with external side effects (changing InDesign's internal state and active page), though with minimal blast radius. It is not Read because it modifies the application state rather than merely retrieving information. It is not Destructive, Write, Financial, or Other.
From the tool's definition Tool name and description 'Navigate to a specific page' indicates triggering a navigation action in Adobe InDesign that changes the active view/selection state. This is a viewpoint manipulation rather than data retrieval alone.
Documented attack patterns abuse exactly the kind of access navigate_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 navigate_to_page:
{
"version": "1",
"default": "deny",
"tools": {
"navigate_to_page": {
"limits": [
{
"counter": "navigate_to_page_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}navigate_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.
Free to start. No card required.
Navigate to a specific page. 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.
Register the InDesign UXP MCP Server MCP server in PolicyLayer and add a rule for navigate_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.
navigate_to_page is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the navigate_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.
Set action: deny in the PolicyLayer policy for navigate_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.
navigate_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.
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.