merge_branch_into_target
Merge A Branch Into A Target Branch.
This record as markdown: /tools/aiwerk-mcp-server-elevenlabs/merge-branch-into-target.md
What merge_branch_into_target does on Elevenlabs
AI agents use merge_branch_into_target to create or update resources in Elevenlabs, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Elevenlabs environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
force | boolean | — | Force source branch changes onto the target, overriding timestamp-based conflict resolution |
agent_id | string | Yes | The id of an agent. This is returned on agent creation. |
source_branch_id | string | Yes | Unique identifier for the source branch to merge from. |
target_branch_id | string | Yes | The ID of the target branch to merge into. |
archive_source_branch | boolean | — | Whether to archive the source branch after merging |
Parameters from the server's own tool schema.
Why merge_branch_into_target is rated Medium
An AI agent can call merge_branch_into_target faster than any human can review: one bad instruction and it creates or modifies resources in Elevenlabs by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs merge_branch_into_target safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Elevenlabs, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For merge_branch_into_target, this is the rule to start with:
merge_branch_into_target 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 Elevenlabs, apply this rule, and every merge_branch_into_target call is checked against it from then on.
Questions about merge_branch_into_target
Merge A Branch Into A Target Branch. It is categorised as a Write tool in the Elevenlabs MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
merge_branch_into_target accepts 5 parameters: force, agent_id, source_branch_id, target_branch_id, archive_source_branch. Required: agent_id, source_branch_id, target_branch_id. The full parameter table on this page comes from the server's own tool schema.
Register the Elevenlabs MCP server in PolicyLayer and add a rule for merge_branch_into_target: 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 Elevenlabs. Nothing to install.
merge_branch_into_target 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 merge_branch_into_target 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 merge_branch_into_target. 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.
merge_branch_into_target is provided by the Elevenlabs MCP server (@aiwerk/mcp-server-elevenlabs). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Elevenlabs, and thousands of servers like it.
This server
Across the catalogue