list_active_addons

List the project owners currently-active add-ons. Returns [{addonKey, project, monthlyEurCents, activatedAt, nextRenewalAt, consecutiveFailures}, ...]. RPM upgrades are per-project; project is the slug they apply to (null for account-wide add-ons). Owner-only; requires a token minted with the bil...

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-active-addons.md

WHAT IT DOES

What list_active_addons does on EchoRelay

AI agents call list_active_addons 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_active_addons is rated Low

This tool retrieves sensitive financial and billing information (addon details, pricing in EUR cents, renewal dates). While it performs no destructive, write, or execute operations, the information returned (billing status, addon keys, renewal schedule) is sensitive enough to warrant medium severity if exposed to an unauthorized agent.

From the tool's definition The tool description explicitly states 'List the project owner's currently-active add-ons' and 'Returns [...]', indicating it retrieves and queries billing/addon data without modification. It is read-only in nature.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

list_active_addons Allowed

list_active_addons 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_active_addons": {}
  }
}

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

FAQ

Questions about list_active_addons

What does the list_active_addons tool do? +

How do I enforce a policy on list_active_addons? +

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

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

Can I rate-limit list_active_addons? +

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

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

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