cancel_line_publish
Cancel one line schedule before its two-minute lock.
This record as markdown: /tools/dev-echorelay-management/cancel-line-publish.md
What cancel_line_publish does on EchoRelay
AI agents call cancel_line_publish 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 | |
draftRevision | integer | Yes |
Parameters from the server's own tool schema.
Why cancel_line_publish is rated Critical
An AI agent that decides to call cancel_line_publish 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.
Attacks that exploit this kind of access
The rule that runs cancel_line_publish 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 cancel_line_publish, this is the rule to start with:
cancel_line_publish 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 cancel_line_publish call is checked against it from then on.
Questions about cancel_line_publish
Cancel one line schedule before its two-minute lock. 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.
cancel_line_publish accepts 2 parameters: lineKey, draftRevision. Required: lineKey, draftRevision. 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 cancel_line_publish: 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.
cancel_line_publish 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 cancel_line_publish 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 cancel_line_publish. 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.
cancel_line_publish 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