list_projects

List the projects on your account (archived included), each with id, slug, name, apiBaseUrl and archived. Requires an ACCOUNT-scoped token (one minted with no project) and the read scope. A project-scoped token cannot call this — use it on its own project's tools instead.

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

WHAT IT DOES

What list_projects does on EchoRelay

AI agents call list_projects 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_projects is rated Low

This tool retrieves account-level project metadata without side effects. It is a pure query operation that returns existing data. The requirement for an ACCOUNT-scoped token with 'read' scope further confirms read-only access. Low severity because the blast radius of an AI agent calling this is minimal—it only enumerates project information the authenticated user already has access to.

From the tool's definition Tool description explicitly states 'List the projects on your account' with fields like id, slug, name, apiBaseUrl and archived status. Uses 'read' scope. No modifications, deletions, or external operations are performed.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

list_projects Allowed

list_projects 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_projects": {}
  }
}

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

FAQ

Questions about list_projects

What does the list_projects tool do? +

How do I enforce a policy on list_projects? +

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

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

Can I rate-limit list_projects? +

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

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

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