ae_create_null_controller
Create null objects with slider controls for advanced animation rigging and control
This record as markdown: /tools/ae/ae-create-null-controller.md
What ae_create_null_controller does on Ae
AI agents use ae_create_null_controller to create or update resources in Ae, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ae environment.
Why ae_create_null_controller is rated Medium
The tool creates new null objects in an After Effects project, which is a reversible modification operation. This falls under Write category (creates/modifies data reversibly). Severity is medium because misuse could clutter a project or create unwanted control structures, but the effects are easily undoable and non-destructive.
From the tool's definition Tool description states 'Create null objects' - the verb 'Create' indicates data creation. This is a creative asset creation operation in After Effects, modifying the project composition by adding new control objects.
Attacks that exploit this kind of access
The rule that runs ae_create_null_controller 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_create_null_controller, this is the rule to start with:
ae_create_null_controller 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Ae, apply this rule, and every ae_create_null_controller call is checked against it from then on.
Questions about ae_create_null_controller
Create null objects with slider controls for advanced animation rigging and control. It is categorised as a Write tool in the Ae MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Ae MCP server in PolicyLayer and add a rule for ae_create_null_controller: 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_create_null_controller 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 ae_create_null_controller 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_create_null_controller. 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_create_null_controller 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