retry_dlq_entry
Re-enqueue a DLQ entry to the main relay stream and delete it from the DLQ. A replay is billed like any relay — it charges the entry's original credit cost to the project before re-sending; if the balance is too low the entry stays in the DLQ and this returns an insufficient-credits error (top up...
This record as markdown: /tools/dev-echorelay-management/retry-dlq-entry.md
What retry_dlq_entry does on EchoRelay
AI agents use retry_dlq_entry to commit financial operations through EchoRelay, usually the final step of a payment, billing, or trading workflow. A call moves real money.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string | Yes | Redis stream id from list_dlq. |
Parameters from the server's own tool schema.
Why retry_dlq_entry is rated Critical
This tool incurs a financial charge (credits deducted from the project balance) as a direct consequence of its operation, placing it in the Financial category. It also deletes the DLQ entry (Destructive), but Financial supersedes Destructive per the severity rules. Misuse could drain project credits by repeatedly re-enqueuing expensive entries.
From the tool's definition A replay is billed like any relay — it charges the entry's original credit cost to the project before re-sending; if the balance is too low the entry stays in the DLQ
Attacks that exploit this kind of access
The rule that runs retry_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 retry_dlq_entry, this is the rule to start with:
Any call to retry_dlq_entry is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect EchoRelay, apply this rule, and every retry_dlq_entry call is checked against it from then on.
Questions about retry_dlq_entry
Re-enqueue a DLQ entry to the main relay stream and delete it from the DLQ. A replay is billed like any relay — it charges the entry's original credit cost to the project before re-sending; if the balance is too low the entry stays in the DLQ and this returns an insufficient-credits error (top up and retry). Succeeds if the entry exists, errors if it's already gone (retried or discarded). Requires edit access. It is categorised as a Financial tool in the EchoRelay MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
retry_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 retry_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.
retry_dlq_entry is a Financial 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 retry_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 retry_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.
retry_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