copy_effect_to_layer

Copy an effect (by name or index) from a source layer to a destination layer, optionally in a different comp.

SERVERAe SOURCE@synthetic-ai/ae-mcp

Medium RISK CLASS

Category Write

Parameters 103 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/synthetic-ai-ae-mcp/copy-effect-to-layer.md

WHAT IT DOES

What copy_effect_to_layer does on Ae

AI agents use copy_effect_to_layer 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.

Parameter	Type	Required	Description
`save`	boolean	—
`timeoutMs`	number	—
`copyValues`	boolean	—	Also copy property values (default true)
`effectName`	string	—
`effectIndex`	number	—	1-based effect index (used if effectName not given)
`projectPath`	string	—
`destCompName`	string	—	Destination comp (defaults to same as source comp)
`destLayerName`	string	Yes
`sourceCompName`	string	Yes
`sourceLayerName`	string	Yes

Parameters from the server's own tool schema.

RISK

Why copy_effect_to_layer is rated Medium

An AI agent can call copy_effect_to_layer faster than any human can review: one bad instruction and it creates or modifies resources in Ae by the hundred, each call as confident as the last.

Risk signalsHigh parameter count (10 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs copy_effect_to_layer 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 copy_effect_to_layer, this is the rule to start with:

copy_effect_to_layer Rate-limited

copy_effect_to_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "copy_effect_to_layer": {
      "limits": [
        {
          "counter": "copy_effect_to_layer_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Ae, apply this rule, and every copy_effect_to_layer call is checked against it from then on.

FAQ

Questions about copy_effect_to_layer

What does the copy_effect_to_layer tool do? +

Copy an effect (by name or index) from a source layer to a destination layer, optionally in a different comp. 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.

What parameters does copy_effect_to_layer accept? +

copy_effect_to_layer accepts 10 parameters: save, timeoutMs, copyValues, effectName, effectIndex, projectPath, destCompName, destLayerName, sourceCompName, sourceLayerName. Required: destLayerName, sourceCompName, sourceLayerName. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on copy_effect_to_layer? +

Register the Ae MCP server in PolicyLayer and add a rule for copy_effect_to_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 Ae. Nothing to install.

What risk level is copy_effect_to_layer? +

copy_effect_to_layer is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit copy_effect_to_layer? +

Yes. Add a rate_limit block to the copy_effect_to_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.

How do I block copy_effect_to_layer completely? +

Set action: deny in the PolicyLayer policy for copy_effect_to_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.

What MCP server provides copy_effect_to_layer? +

copy_effect_to_layer is provided by the Ae MCP server (@synthetic-ai/ae-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Ae, and thousands of servers like it.

This server

All 226 Ae tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →