discard_dlq_entry
Permanently delete a DLQ entry without retrying. Requires edit access.
This record as markdown: /tools/dev-echorelay-management/discard-dlq-entry.md
What discard_dlq_entry does on EchoRelay
AI agents call discard_dlq_entry 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 |
|---|---|---|---|
id | string | Yes | Redis stream id from list_dlq. |
Parameters from the server's own tool schema.
Why discard_dlq_entry is rated Critical
This tool irreversibly removes data (DLQ entries) with no undo capability. DLQ (Dead Letter Queue) entries represent failed messages that may be critical for debugging or recovery. Permanent deletion without retry options means lost message history and potential loss of important operational data.
From the tool's definition Tool description states 'Permanently delete a DLQ entry without retrying' and requires 'edit access'. The word 'Permanently delete' and the irreversible nature of the operation (DLQ entry removal) classify this as destructive.
Attacks that exploit this kind of access
The rule that runs discard_dlq_entry 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 discard_dlq_entry, this is the rule to start with:
discard_dlq_entry 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 discard_dlq_entry call is checked against it from then on.
Questions about discard_dlq_entry
Permanently delete a DLQ entry without retrying. 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.
discard_dlq_entry accepts 1 parameter: id. Required: id. 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 discard_dlq_entry: 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.
discard_dlq_entry 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 discard_dlq_entry 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 discard_dlq_entry. 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.
discard_dlq_entry 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