delete_line
Delete a line and every endpoint under it, publishing the removal immediately. Requires edit access.
This record as markdown: /tools/dev-echorelay-management/delete-line.md
What delete_line does on EchoRelay
AI agents call delete_line to permanently remove resources in EchoRelay, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
lineKey | string | Yes | The line key, e.g. "v1". |
commitMode | string | — | Defaults to publish. Draft writes require draftRevision. |
draftRevision | integer | — | Current line draft revision, required for draft writes. |
Parameters from the server's own tool schema.
Why delete_line is rated Critical
An AI agent that decides to call delete_line doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from EchoRelay is gone. There is no undo for destructive operations.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs delete_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 delete_line, this is the rule to start with:
delete_line is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect EchoRelay, apply this rule, and every delete_line call is checked against it from then on.
Questions about delete_line
Delete a line and every endpoint under it, publishing the removal immediately. Requires edit access. It is categorised as a Destructive tool in the EchoRelay MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
delete_line accepts 3 parameters: lineKey, commitMode, draftRevision. Required: lineKey. 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 delete_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.
delete_line is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_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 delete_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.
delete_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