deactivate_line
Take a line off the data plane immediately (callers get 404) without deleting it — endpoints/targets/config are preserved and it can be reactivated later. A deliberate action; live traffic is never auto-disabled. Requires edit access.
This record as markdown: /tools/dev-echorelay-management/deactivate-line.md
What deactivate_line does on EchoRelay
AI agents use deactivate_line to create or update resources in EchoRelay, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your EchoRelay environment.
| 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 deactivate_line is rated Medium
An AI agent can call deactivate_line faster than any human can review: one bad instruction and it creates or modifies resources in EchoRelay by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs deactivate_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 deactivate_line, this is the rule to start with:
deactivate_line 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 EchoRelay, apply this rule, and every deactivate_line call is checked against it from then on.
Questions about deactivate_line
Take a line off the data plane immediately (callers get 404) without deleting it — endpoints/targets/config are preserved and it can be reactivated later. A deliberate action; live traffic is never auto-disabled. Requires edit access. It is categorised as a Write tool in the EchoRelay MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
deactivate_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 deactivate_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.
deactivate_line 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 deactivate_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 deactivate_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.
deactivate_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.
This server
Across the catalogue