list_audit_events
List project audit-log entries, newest first. Captures who changed what — lines, endpoints, targets, API keys. Outbound-target auth.token / auth.password are redacted in the diff per the same policy used for endpoint reads. Retention is the auditRetentionDays advertised on get_project (default 36...
This record as markdown: /tools/dev-echorelay-management/list-audit-events.md
What list_audit_events does on EchoRelay
AI agents call list_audit_events 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 |
|---|---|---|---|
limit | integer | — | Page size. Default 50. |
since | integer | — | Lower bound on createdAt (unix ms). Inclusive. |
until | integer | — | Upper bound on createdAt (unix ms). Inclusive. |
action | string | — | Exact action match, e.g. "endpoint.updated", "target.created", "key.revoked". |
offset | integer | — | Page offset. Default 0. |
entityId | string | — | Exact entity id (UUID or stream id depending on entityType). |
entityType | string | — | Exact entity type, e.g. "endpoint", "target", "line", "key". |
Parameters from the server's own tool schema.
Why list_audit_events is rated Low
This tool retrieves audit log entries without modifying, deleting, or executing any operations. It is a query function that provides visibility into historical changes. While audit logs may contain sensitive information about who changed what, the tool itself only reads and returns this data without side effects.
From the tool's definition Tool description states 'List project audit-log entries' and returns read-only audit log data with `{total, limit, offset, retentionDays, rows[]}`.
Attacks that exploit this kind of access
The rule that runs list_audit_events 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_audit_events, this is the rule to start with:
list_audit_events 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_audit_events call is checked against it from then on.
Questions about list_audit_events
List project audit-log entries, newest first. Captures who changed what — lines, endpoints, targets, API keys. Outbound-target auth.token / auth.password are redacted in the diff per the same policy used for endpoint reads. Retention is the auditRetentionDays advertised on get_project (default 365 days); rows older than that are purged by the cleanup job. Returns {total, limit, offset, retentionDays, rows[]} where each row has id, createdAt, actor (email or null), action, entityType, entityId, entityLabel, diff. It is categorised as a Read tool in the EchoRelay MCP Server, which means it retrieves data without modifying state.
list_audit_events accepts 7 parameters: limit, since, until, action, offset, entityId, entityType. 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_audit_events: 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_audit_events 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_audit_events 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_audit_events. 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_audit_events 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