indesign_add_item_to_group
InDesign: Add a top-level page item to an existing group (the group is rebuilt: it keeps its name but gets a new ID and index)
This record as markdown: /tools/adobe-mcp-suite/indesign-add-item-to-group.md
What indesign_add_item_to_group does on Adobe Mcp Suite
AI agents use indesign_add_item_to_group to create or update resources in Adobe Mcp Suite, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Adobe Mcp Suite environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
itemIndex | integer | Yes | Index of the page item to add to the group, in page.allPageItems as numbered by list_page_items (nested items included) |
pageIndex | integer | Yes | Index of the page containing the group and item (0-based) |
groupIndex | integer | Yes | Index of the group to add the item to, as numbered by list_groups (its index in page.allPageItems) |
Parameters from the server's own tool schema.
Why indesign_add_item_to_group is rated Medium
An AI agent can call indesign_add_item_to_group faster than any human can review: one bad instruction and it creates or modifies resources in Adobe Mcp Suite by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs indesign_add_item_to_group 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_add_item_to_group, this is the rule to start with:
indesign_add_item_to_group stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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_add_item_to_group call is checked against it from then on.
Questions about indesign_add_item_to_group
InDesign: Add a top-level page item to an existing group (the group is rebuilt: it keeps its name but gets a new ID and index). It is categorised as a Write tool in the Adobe Mcp Suite MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
indesign_add_item_to_group accepts 3 parameters: itemIndex, pageIndex, groupIndex. Required: itemIndex, pageIndex, groupIndex. 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_add_item_to_group: 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_add_item_to_group is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the indesign_add_item_to_group 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_add_item_to_group. 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_add_item_to_group 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