indesign_remove_item_from_group
InDesign: Remove a member from a group (the group is rebuilt with the remaining members, or dissolved if fewer than 2 remain)
This record as markdown: /tools/adobe-mcp-suite/indesign-remove-item-from-group.md
What indesign_remove_item_from_group does on Adobe Mcp Suite
AI agents call indesign_remove_item_from_group to permanently remove resources in Adobe Mcp Suite, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
itemIndex | integer | Yes | Index of the member within the group (group.pageItems), as listed by get_group_info; not the list_page_items numbering |
pageIndex | integer | Yes | Index of the page containing the group (0-based) |
groupIndex | integer | Yes | Index of the group to remove the item from, as numbered by list_groups (its index in page.allPageItems) |
Parameters from the server's own tool schema.
Why indesign_remove_item_from_group is rated Critical
An AI agent that decides to call indesign_remove_item_from_group doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Adobe Mcp Suite is gone. There is no undo for destructive operations.
Attacks that exploit this kind of access
The rule that runs indesign_remove_item_from_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_remove_item_from_group, this is the rule to start with:
indesign_remove_item_from_group is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Adobe Mcp Suite, apply this rule, and every indesign_remove_item_from_group call is checked against it from then on.
Questions about indesign_remove_item_from_group
InDesign: Remove a member from a group (the group is rebuilt with the remaining members, or dissolved if fewer than 2 remain). It is categorised as a Destructive tool in the Adobe Mcp Suite MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
indesign_remove_item_from_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_remove_item_from_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_remove_item_from_group is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the indesign_remove_item_from_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_remove_item_from_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_remove_item_from_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.
Across the catalogue