indesign_data_merge
InDesign: Data merge: select a CSV or tab-delimited text data source for the active document and (optionally) merge records. The document must already contain data merge placeholders for merging to succeed.
This record as markdown: /tools/adobe-mcp-suite/indesign-data-merge.md
What indesign_data_merge does on Adobe Mcp Suite
AI agents call indesign_data_merge to retrieve information from Adobe Mcp Suite without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
dataSource | string | Yes | Absolute path to the data source file (.csv or tab-delimited .txt) |
recordRange | string | — | Record range when recordSelection is RANGE, e.g. "1-5,8" |
mergeRecords | boolean | — | Merge records after selecting the data source. If false, only selects the source and lists its fields. |
recordNumber | integer | — | Record to merge when recordSelection is ONE_RECORD |
recordsPerPage | string | — | One record per page, or multiple records per page |
recordSelection | string | — | Which records to merge |
removeBlankLines | boolean | — | Remove blank lines caused by empty fields |
createNewDocument | boolean | — | Create a new document for the merged records |
Parameters from the server's own tool schema.
Why indesign_data_merge is rated Low
Even though indesign_data_merge only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs indesign_data_merge 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_data_merge, this is the rule to start with:
indesign_data_merge is read-only, so it stays allowed. 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_data_merge call is checked against it from then on.
Questions about indesign_data_merge
InDesign: Data merge: select a CSV or tab-delimited text data source for the active document and (optionally) merge records. The document must already contain data merge placeholders for merging to succeed. It is categorised as a Read tool in the Adobe Mcp Suite MCP Server, which means it retrieves data without modifying state.
indesign_data_merge accepts 8 parameters: dataSource, recordRange, mergeRecords, recordNumber, recordsPerPage, recordSelection, removeBlankLines, createNewDocument. Required: dataSource. 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_data_merge: 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_data_merge is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the indesign_data_merge 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_data_merge. 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_data_merge 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.
This server
Across the catalogue