batch_replace_footage
Replace multiple footage items by mapping old filename patterns to new absolute file paths.
This record as markdown: /tools/synthetic-ai-ae-mcp/batch-replace-footage.md
What batch_replace_footage does on Ae
AI agents use batch_replace_footage 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 | — | |
projectPath | string | — | |
replacements | array | Yes | Array of {oldName, newPath} objects. oldName is matched against footage item names (substring match). newPath is the absolute path to the replacement file. |
Parameters from the server's own tool schema.
Why batch_replace_footage is rated Medium
An AI agent can call batch_replace_footage 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 signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs batch_replace_footage 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 batch_replace_footage, this is the rule to start with:
batch_replace_footage 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 batch_replace_footage call is checked against it from then on.
Questions about batch_replace_footage
Replace multiple footage items by mapping old filename patterns to new absolute file paths. 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.
batch_replace_footage accepts 4 parameters: save, timeoutMs, projectPath, replacements. Required: replacements. The full parameter table on this page comes from the server's own tool schema.
Register the Ae MCP server in PolicyLayer and add a rule for batch_replace_footage: 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.
batch_replace_footage 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 batch_replace_footage 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 batch_replace_footage. 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.
batch_replace_footage 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.
More on Ae, and thousands of servers like it.
This server
Across the catalogue