AI agents invoke navigate_to_page to trigger actions in InDesign 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.
This tool executes a navigation operation with side effects (changing application state/focus) but does not read, write, delete, or move money. It is reversible and has limited blast radius—navigation alone cannot corrupt data or cause financial harm. Classified as Execute rather than Write because it doesn't persist data modifications, only triggers an application state transition.
From the tool's definition Tool performs an action that 'Navigate to a specific page' - a directional/operational command that triggers a state change in the InDesign application by moving focus or viewport position to a designated page.
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 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 MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the InDesign 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 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 MCP Server MCP server (zachshallbetter/indesign-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from InDesign MCP Server, 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.
135 InDesign MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.