This record as markdown: /tools/ae/ae-select-layers.md
What ae_select_layers does on Ae
AI agents invoke ae_select_layers to trigger actions in Ae. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why ae_select_layers is rated High
This tool changes the selection state within Adobe After Effects, which is an application-side action that triggers a UI/state change and enables subsequent operations. It is not purely reading data — it actively modifies the application's selection state, which can affect what operations are applied next.
From the tool's definition Select one or more layers in the composition for subsequent operations
Attacks that exploit this kind of access
The rule that runs ae_select_layers safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ae, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For ae_select_layers, this is the rule to start with:
ae_select_layers stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Ae, apply this rule, and every ae_select_layers call is checked against it from then on.
Questions about ae_select_layers
Select one or more layers in the composition for subsequent operations. It is categorised as a Execute tool in the Ae MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Ae MCP server in PolicyLayer and add a rule for ae_select_layers: 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 Ae. Nothing to install.
ae_select_layers is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the ae_select_layers 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 ae_select_layers. 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.
ae_select_layers is provided by the Ae MCP server (ae-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ae, and thousands of servers like it.
This server
Across the catalogue