duplicate_line
Copy a line and all its endpoints/targets/rules into a new line key — build v2 from v1. The copy is saved inactive and remains off the data plane; edit it, then activate_line when ready. Requires edit access.
This record as markdown: /tools/dev-echorelay-management/duplicate-line.md
What duplicate_line does on EchoRelay
AI agents invoke duplicate_line to trigger actions in EchoRelay. 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | — | Optional name for the copy (defaults to "<source name> (copy)"). |
lineKey | string | Yes | The source line key to copy. |
commitMode | string | — | Defaults to publish. Draft writes require draftRevision. |
newLineKey | string | Yes | New line key for the copy, e.g. "v2". |
draftRevision | integer | — | Current line draft revision, required for draft writes. |
Parameters from the server's own tool schema.
Why duplicate_line is rated High
duplicate_line triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.
Attacks that exploit this kind of access
The rule that runs duplicate_line safely
PolicyLayer is an MCP gateway: it sits between your AI agents and EchoRelay, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For duplicate_line, this is the rule to start with:
duplicate_line 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 EchoRelay, apply this rule, and every duplicate_line call is checked against it from then on.
Questions about duplicate_line
Copy a line and all its endpoints/targets/rules into a new line key — build v2 from v1. The copy is saved inactive and remains off the data plane; edit it, then activate_line when ready. Requires edit access. It is categorised as a Execute tool in the EchoRelay MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
duplicate_line accepts 5 parameters: name, lineKey, commitMode, newLineKey, draftRevision. Required: lineKey, newLineKey. The full parameter table on this page comes from the server's own tool schema.
Register the EchoRelay MCP server in PolicyLayer and add a rule for duplicate_line: 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 EchoRelay. Nothing to install.
duplicate_line 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 duplicate_line 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 duplicate_line. 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.
duplicate_line is provided by the EchoRelay MCP server (https://mcp.echorelay.dev). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on EchoRelay, and thousands of servers like it.
Across the catalogue