AI agents use move_spread to create or update resources in InDesign UXP MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your InDesign UXP MCP Server environment.
This tool modifies document structure by reordering spreads, which is a reversible operation. It does not delete data (which would be Destructive), execute arbitrary code (Execute), involve financial transactions (Financial), or merely read data (Read). The blast radius is medium because document reordering could disrupt layout and workflow, but the action is easily undone via undo or by moving the spread back.
From the tool's definition Tool name 'move_spread' and description 'Move a spread to a different position' indicates it modifies the structure and ordering of document content within InDesign by repositioning spreads.
Documented attack patterns abuse exactly the kind of access move_spread gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and InDesign UXP MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for move_spread:
{
"version": "1",
"default": "deny",
"tools": {
"move_spread": {
"limits": [
{
"counter": "move_spread_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}move_spread 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.
Free to start. No card required.
Move a spread to a different position. It is categorised as a Write tool in the InDesign UXP MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the InDesign UXP MCP Server MCP server in PolicyLayer and add a rule for move_spread: 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 UXP MCP Server. Nothing to install.
move_spread 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 move_spread 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 move_spread. 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.
move_spread is provided by the InDesign UXP MCP Server MCP server (theloniuser/indesign-uxp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 135 InDesign UXP MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
135 InDesign UXP MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.