indesign_preflight_document
InDesign: Run a preflight check on the active document with a preflight profile and list the problems found (optionally saving a report)
This record as markdown: /tools/adobe-mcp-suite/indesign-preflight-document.md
What indesign_preflight_document does on Adobe Mcp Suite
AI agents invoke indesign_preflight_document to trigger actions in Adobe Mcp Suite. 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
profile | string | — | Preflight profile name, e.g. "[Basic]" (the built-in profile). Embedded document profiles are checked first, then application profiles. |
maxResults | integer | — | Maximum number of problems to list |
reportPath | string | — | Optional absolute path to save the preflight report (.pdf or .txt) |
timeoutSeconds | integer | — | Maximum seconds to wait for preflight to finish |
Parameters from the server's own tool schema.
Why indesign_preflight_document is rated High
indesign_preflight_document triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.
Attacks that exploit this kind of access
The rule that runs indesign_preflight_document safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Adobe Mcp Suite, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For indesign_preflight_document, this is the rule to start with:
indesign_preflight_document 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Adobe Mcp Suite, apply this rule, and every indesign_preflight_document call is checked against it from then on.
Questions about indesign_preflight_document
InDesign: Run a preflight check on the active document with a preflight profile and list the problems found (optionally saving a report). It is categorised as a Execute tool in the Adobe Mcp Suite MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
indesign_preflight_document accepts 4 parameters: profile, maxResults, reportPath, timeoutSeconds. The full parameter table on this page comes from the server's own tool schema.
Register the Adobe Mcp Suite MCP server in PolicyLayer and add a rule for indesign_preflight_document: 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 Adobe Mcp Suite. Nothing to install.
indesign_preflight_document 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 indesign_preflight_document 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 indesign_preflight_document. 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.
indesign_preflight_document is provided by the Adobe Mcp Suite MCP server (adobe-mcp-suite). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Adobe Mcp Suite, and thousands of servers like it.
Across the catalogue