AI agents use place_file_on_page 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 creates/inserts new content (a placed file/image) into a document, which is a reversible modification operation. It does not execute arbitrary code, delete content, or move money, so it falls under Write rather than Execute or Destructive. Severity is medium because misuse could degrade document integrity or introduce unwanted assets, but the change can be undone via undo/delete operations.
From the tool's definition Tool name 'place_file_on_page' and description 'Place a file on a page' indicate insertion of external content into an InDesign document, modifying its structure and composition.
Documented attack patterns abuse exactly the kind of access place_file_on_page 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 place_file_on_page:
{
"version": "1",
"default": "deny",
"tools": {
"place_file_on_page": {
"limits": [
{
"counter": "place_file_on_page_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}place_file_on_page 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.
Place a file on a page. 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 place_file_on_page: 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.
place_file_on_page 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 place_file_on_page 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 place_file_on_page. 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.
place_file_on_page 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.