New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

list_dlq

List entries currently in this project's dead-letter queue, newest first. One inbound request fans out per-target, so a single failed request may produce several DLQ entries with different targetIds. Returns {total, limit, offset, rows[]} where each row has id (Redis stream id), requestId, target...

SERVEREchoRelay SOURCEhttps://mcp.echorelay.dev
Low RISK CLASS
Category Read
Parameters 20 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/dev-echorelay-management/list-dlq.md

What list_dlq does on EchoRelay

AI agents call list_dlq 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.

ParameterTypeRequiredDescription
limit integer Page size. Default 50.
offset integer Page offset. Default 0.

Parameters from the server's own tool schema.

Why list_dlq is rated Low

This tool retrieves and queries DLQ (dead-letter queue) entries for inspection and monitoring purposes. It has no side effects, does not modify or delete data, and does not execute operations. The description explicitly indicates it only lists/returns existing entries.

From the tool's definition Tool description states 'List entries currently in this project's dead-letter queue' and 'Returns {total, limit, offset, rows[]}'. The verb 'list' and return-only behavior indicate data retrieval with no modifications.

Questions about list_dlq

What does the list_dlq tool do? +

List entries currently in this project's dead-letter queue, newest first. One inbound request fans out per-target, so a single failed request may produce several DLQ entries with different targetIds. Returns {total, limit, offset, rows[]} where each row has id (Redis stream id), requestId, targetId, failureReason, failedAttempts, failedAt, payload (the original Consumer queue entry JSON). DLQ entries — including the original request body and headers — are kept for up to 30 days from the failure time or until cleared, then purged automatically; they are never written to a database. It is categorised as a Read tool in the EchoRelay MCP Server, which means it retrieves data without modifying state.

What parameters does list_dlq accept? +

list_dlq accepts 2 parameters: limit, offset. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on list_dlq? +

Register the EchoRelay MCP server in PolicyLayer and add a rule for list_dlq: 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.

What risk level is list_dlq? +

list_dlq is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_dlq? +

Yes. Add a rate_limit block to the list_dlq 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.

How do I block list_dlq completely? +

Set action: deny in the PolicyLayer policy for list_dlq. 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.

What MCP server provides list_dlq? +

list_dlq 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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of EchoRelay's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.