AI agents use set_active_layer 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.
Setting an active layer changes the document's editing context but does not create, destroy, or permanently modify content. It is a stateful Write operation with minimal blast radius—an agent could select wrong layers, but the action is fully reversible by selecting a different layer. No data is lost, no external operations triggered, and no financial implications.
From the tool's definition Tool name 'set_active_layer' and description 'Set the active layer' indicate modification of document state (which layer is currently active for editing). This is a reversible state change without data creation/deletion.
Documented attack patterns abuse exactly the kind of access set_active_layer 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 set_active_layer:
{
"version": "1",
"default": "deny",
"tools": {
"set_active_layer": {
"limits": [
{
"counter": "set_active_layer_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}set_active_layer 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.
Set the active layer. 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 set_active_layer: 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.
set_active_layer 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 set_active_layer 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 set_active_layer. 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.
set_active_layer 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.