list_members

List accepted and pending members of this project. Shows name/email, role, and whether the invite has been accepted. Owner only.

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-members.md

WHAT IT DOES

What list_members does on EchoRelay

AI agents call list_members 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_members is rated Low

This tool retrieves and displays project membership information without creating, modifying, or deleting data. It is a read-only query operation with limited blast radius even if misused by an AI agent, as it only exposes project member metadata that the owner could already view through the UI.

From the tool's definition Tool name is 'list_members' and description states it 'List[s] accepted and pending members' — a retrieval operation with no modification or side effects. The 'Owner only' access control does not change the fundamental action of querying/listing data.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

list_members Allowed

list_members 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_members": {}
  }
}

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_members call is checked against it from then on.

FAQ

Questions about list_members

What does the list_members tool do? +

List accepted and pending members of this project. Shows name/email, role, and whether the invite has been accepted. Owner only. 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_members? +

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

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

Can I rate-limit list_members? +

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

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

list_members 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 →