get_dlq_entry
Get a single DLQ entry by its Redis stream id ({ms}-{seq}, as returned by list_dlq). DLQ entries are retained for up to 30 days from the failure time or until cleared; this returns null if the entry has been purged or discarded.
This record as markdown: /tools/dev-echorelay-management/get-dlq-entry.md
What get_dlq_entry does on EchoRelay
AI agents call get_dlq_entry to retrieve information from EchoRelay without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string | Yes | Redis stream id, e.g. "1717930000000-0". |
Parameters from the server's own tool schema.
Why get_dlq_entry is rated Low
This tool retrieves a single Dead Letter Queue (DLQ) entry by ID from what appears to be a Redis stream. The operation is read-only with no capability to modify, delete, or trigger external actions. The worst-case misuse is information disclosure of failed message data, which constitutes low risk. Classification: Read/low.
From the tool's definition Tool name 'get_dlq_entry' and description 'Get a single DLQ entry' indicate retrieval of data. No modifications, deletions, or side effects are described. Returns null if entry is absent, confirming it is a query operation.
Attacks that exploit this kind of access
The rule that runs get_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 get_dlq_entry, this is the rule to start with:
get_dlq_entry is read-only, so it stays allowed. 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 get_dlq_entry call is checked against it from then on.
Questions about get_dlq_entry
Get a single DLQ entry by its Redis stream id ({ms}-{seq}, as returned by list_dlq). DLQ entries are retained for up to 30 days from the failure time or until cleared; this returns null if the entry has been purged or discarded. It is categorised as a Read tool in the EchoRelay MCP Server, which means it retrieves data without modifying state.
get_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 get_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.
get_dlq_entry is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_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 get_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.
get_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.
This server
Across the catalogue