list_requests
List inbound API requests the relay has processed for this project, newest first. Hot-tier window is the project's requestLogRetentionDays (see get_project). Optional filters narrow the result. Returns {total, limit, offset, rows[]} where each row has ts (unix ms), requestId, method, path, status...
This record as markdown: /tools/dev-echorelay-management/list-requests.md
What list_requests does on EchoRelay
AI agents call list_requests 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 |
|---|---|---|---|
path | string | — | Substring of the request path (e.g. "/webhook"). LIKE-matched. |
limit | integer | — | Page size. Default 50. |
since | integer | — | Lower bound on ts (unix ms). Inclusive. |
until | integer | — | Upper bound on ts (unix ms). Inclusive. |
method | string | — | HTTP method (POST, GET, …). Case-insensitive. |
offset | integer | — | Page offset. Default 0. |
status | integer | — | Exact HTTP status code (e.g. 404). |
targetOutcome | string | — | Narrow to requests that produced at least one per-target attempt with this outcome. Use "dlq" to find requests with at least one target that ended up dead-lette |
Parameters from the server's own tool schema.
Why list_requests is rated Low
This tool retrieves and queries historical request logs for a project with optional filtering. It is a read-only operation that returns data without side effects. The logs are already stored and the tool simply surfaces them, making it clearly a Read category operation with low risk.
From the tool's definition Tool description states 'List inbound API requests the relay has processed' and 'Returns {total, limit, offset, rows[]}' with query-like structure including optional filters. No modifications, deletions, or external operations are performed.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs list_requests 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 list_requests, this is the rule to start with:
list_requests 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 list_requests call is checked against it from then on.
Questions about list_requests
List inbound API requests the relay has processed for this project, newest first. Hot-tier window is the project's requestLogRetentionDays (see get_project). Optional filters narrow the result. Returns {total, limit, offset, rows[]} where each row has ts (unix ms), requestId, method, path, status, durationMs, targets, creditsDeducted, authType, errorMessage, bytesSent, closeReason (for a streaming request: complete / abortedOrError / byteCap / noValue; empty for non-stream requests). It is categorised as a Read tool in the EchoRelay MCP Server, which means it retrieves data without modifying state.
list_requests accepts 8 parameters: path, limit, since, until, method, offset, status, targetOutcome. 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 list_requests: 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.
list_requests 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 list_requests 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 list_requests. 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.
list_requests 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