rollback_config
Publish a retained line revision immediately and clear any pending schedule.
This record as markdown: /tools/dev-echorelay-management/rollback-config.md
What rollback_config does on EchoRelay
AI agents call rollback_config 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 | |
revision | integer | Yes |
Parameters from the server's own tool schema.
Why rollback_config is rated Critical
An AI agent that decides to call rollback_config 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 rollback_config 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 rollback_config, this is the rule to start with:
rollback_config 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 rollback_config call is checked against it from then on.
Questions about rollback_config
Publish a retained line revision immediately and clear any pending schedule. 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.
rollback_config accepts 2 parameters: lineKey, revision. Required: lineKey, revision. 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 rollback_config: 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.
rollback_config 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 rollback_config 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 rollback_config. 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.
rollback_config 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