list_endpoints

List the endpoints under one line of the project.

SERVEREchoRelay SOURCEhttps://mcp.echorelay.dev

Low RISK CLASS

Category Read

Parameters 11 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What list_endpoints does on EchoRelay

AI agents call list_endpoints 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
`lineKey`	string	Yes	The line key, e.g. "v1".

Parameters from the server's own tool schema.

RISK

Why list_endpoints is rated Low

This tool queries and retrieves endpoint data associated with a project line. It performs no side effects, creates no resources, modifies no state, and poses no financial or destructive risk. It is a straightforward read operation that returns information.

From the tool's definition Tool name 'list_endpoints' and description 'List the endpoints under one line of the project' indicate a retrieval operation with no data modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

list_endpoints Allowed

list_endpoints 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_endpoints": {}
  }
}

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

FAQ

Questions about list_endpoints

What does the list_endpoints tool do? +

List the endpoints under one line of the project. It is categorised as a Read tool in the EchoRelay MCP Server, which means it retrieves data without modifying state.

What parameters does list_endpoints accept? +

list_endpoints accepts 1 parameter: lineKey. Required: lineKey. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on list_endpoints? +

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

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

Can I rate-limit list_endpoints? +

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

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

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