list_api_keys

List the project's inbound API keys (metadata only — the secret plaintext is never returned).

SERVEREchoRelay SOURCEhttps://mcp.echorelay.dev

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What list_api_keys does on EchoRelay

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

RISK

Why list_api_keys is rated Low

This tool retrieves and queries API key metadata without returning sensitive plaintext secrets or enabling modification, deletion, or execution. It has no side effects and poses minimal risk if misused by an agent, as metadata alone cannot be used to compromise the system. Classification as Read with low severity is appropriate.

From the tool's definition Tool name is 'list_api_keys' and description states 'List the project's inbound API keys (metadata only — the secret plaintext is never returned).' The word 'List' and explicit statement that only metadata is returned with no secrets exposed indicates a…

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_api_keys 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_api_keys, this is the rule to start with:

list_api_keys Allowed

list_api_keys is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_api_keys": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect EchoRelay, apply this rule, and every list_api_keys call is checked against it from then on.

FAQ

Questions about list_api_keys

What does the list_api_keys tool do? +

List the project's inbound API keys (metadata only — the secret plaintext is never returned). It is categorised as a Read tool in the EchoRelay MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_api_keys? +

Register the EchoRelay MCP server in PolicyLayer and add a rule for list_api_keys: 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_api_keys? +

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

Can I rate-limit list_api_keys? +

Yes. Add a rate_limit block to the list_api_keys 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_api_keys completely? +

Set action: deny in the PolicyLayer policy for list_api_keys. 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_api_keys? +

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

KEEP EXPLORING

More on EchoRelay, and thousands of servers like it.

This server

All 78 EchoRelay tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →