list_project_tokens
List the API tokens scoped to a project you own (any holder): id, label, scopes, createdAt, lastUsedAt, expiresAt, revokedAt — never the secret (only its hash is stored). Requires an ACCOUNT-scoped token and the read scope.
This record as markdown: /tools/dev-echorelay-management/list-project-tokens.md
What list_project_tokens does on EchoRelay
AI agents call list_project_tokens 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 |
|---|---|---|---|
slug | string | Yes | The slug of a project you own. |
Parameters from the server's own tool schema.
Why list_project_tokens is rated Low
This tool retrieves metadata about API tokens (id, label, scopes, timestamps, revocation status) without modifying any data or exposing secrets. It is a straightforward read operation that queries existing token information. The fact that it only returns hashes of secrets (not the secrets themselves) further limits its risk profile.
From the tool's definition Tool description explicitly states 'List the API tokens' and 'never the secret (only its hash is stored)'. The name 'list_project_tokens' and the verb 'List' confirm retrieval without modification. Requires 'read' scope.
Attacks that exploit this kind of access
The rule that runs list_project_tokens 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_project_tokens, this is the rule to start with:
list_project_tokens 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_project_tokens call is checked against it from then on.
Questions about list_project_tokens
List the API tokens scoped to a project you own (any holder): id, label, scopes, createdAt, lastUsedAt, expiresAt, revokedAt — never the secret (only its hash is stored). Requires an ACCOUNT-scoped token and the read scope. It is categorised as a Read tool in the EchoRelay MCP Server, which means it retrieves data without modifying state.
list_project_tokens accepts 1 parameter: slug. Required: slug. 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_project_tokens: 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_project_tokens 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_project_tokens 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_project_tokens. 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_project_tokens 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