New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

EchoRelay

78 tools. 49 can modify or destroy data without limits.

19 destructive tools with no built-in limits. Policy required.

Last updated:

49 can modify or destroy data
29 read-only
78 tools total

Community server · catalogue entry checked 18/08/2026 · full schemas captured for 62 of 78 tools

How to control EchoRelay ↓

What EchoRelay exposes to your agents

Read (29) Write / Execute (30) Destructive / Financial (19)

What EchoRelay costs in tokens

20,913 tokens of tool definitions, loaded on every request
10% of a 200k context window
3,798 heaviest tool: dry_run_endpoint
Critical Risk

The most dangerous EchoRelay tools

49 of EchoRelay's 78 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

How to control EchoRelay

PolicyLayer is an MCP gateway — it sits between your AI agents and EchoRelay, and nothing reaches the server without passing your rules. These are the rules we recommend:

Block financial tools by default
{
  "cancel_subscription": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Requires human approval."
      }
    ]
  }
}

Financial tools should be explicitly enabled per use case, not open by default.

Deny destructive operations
{
  "cancel_line_publish": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations
{
  "activate_line": {
    "limits": [
      {
        "counter": "activate_line_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations
{
  "default_endpoint_template": {
    "limits": [
      {
        "counter": "default_endpoint_template_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

  1. Create a free account and register EchoRelay — nothing to install.
  2. Add these rules — paste them, or build them visually. Tune the limits to your setup.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
ENFORCE POLICY ON ECHORELAY →

Instant setup, no code required.

All 78 EchoRelay tools

WRITE 28 tools
Write activate_line Activate and immediately publish an inactive line so it serves traffic again. Blocked at the active-line cap — Write archive_project Archive a project you own. Reversible: the project + slug persist and credits are kept, but the data plane dro Write config_diff Preview what Save & Publish (or the pending scheduled publish, if one exists) would change: added/removed/chan Write create_api_key Mint an inbound relay (data-plane) API key for callers to send traffic to this project. Its er_live_ or er_tes Write create_credential Save a new reusable credential, sealed with the project's encryption key at write time. Neither this call nor Write create_endpoint Create an endpoint under a line. Defaults to immediate publish; draft mode requires draftRevision. scheduledAt Write create_line Create a new versioned line. Defaults to immediate publish; draft mode requires draftRevision 0. Requires edit Write create_project Create a new project on your account so an agent can bootstrap from a fresh account. The slug is derived from Write create_project_token Mint a PROJECT-scoped management token (er_mcp_) for MCP and REST; it cannot authenticate relay traffic. Use i Write deactivate_line Take a line off the data plane immediately (callers get 404) without deleting it — endpoints/targets/config ar Write invite_member Invite a person by email to collaborate on this project. Returns the new invitation record; the invitee receiv Write preview_line_draft Preview one line draft without publishing it. Write protect_project Turn on archive protection for a project you own: archive_project (on every surface — panel, REST, and this to Write publish_line_draft Publish one line draft now and clear only its schedule. Write rename_project Rename a project you own (the display name only — the slug, which is the identity in URLs / Redis, never chang Write resend_invite Re-send the invitation email for a still-pending invite, by member ID or email (from list_members). The origin Write resume_addon Resume (un-cancel) a pending-cancel add-on whose paid-through cycle has not yet ended. Clears the cancellation Write rotate_api_key Mint a linked successor for an existing key. Returns the successor plaintext exactly once — store it now. The Write schedule_line_publish Schedule one non-empty line draft. Active subscribers required. Write set_burst_opt_in Enable or disable the auto-decaying burst window for live traffic and publish the change immediately. When ena Write set_docs_shared Turn the line's public OpenAPI docs on or off. When enabled, the line's spec is published at docs.{baseDomain} Write set_key_policy Owner-only. Edit the project's key policy. Only fields present in the patch are touched. Editors calling this Write set_member_role Change a member's role between editor, viewer, and billing. Identify the member by their member ID or email (f Write set_outbound_allowlist Narrow the project's outbound host allowlist — the hosts a target may point at. The current list is on get_pro Write set_rpm_ceiling Set or clear a self-set ceiling on this project's own effective live-traffic RPM (Traffic shaping) — for when Write unarchive_project Restore an archived project you own to the data plane. Restoring consumes one of your plan's active-project sl Write update_credential Rename a credential and/or rotate its secret, publishing the change immediately so every target that uses this Write update_endpoint Update an endpoint immediately or in its line draft. The patch is merged field-by-field. Requires edit access.
READ 29 tools
Read default_endpoint_template Return a canonical minimal-valid endpoint JSON for a fresh line. POST it verbatim to create_endpoint to land a Read get_billing Get the project's credit balances (paid + testing) and which ledger it settles on. billingModel is prepaid (me Read get_config Get the project's published relay configuration — the exact JSON the EchoRelay Framework consumes. Includes pe Read get_dlq_entry Get DLQ entries by Redis stream id ({ms}-{seq}, as returned by list_dlq's id) or by requestId. requestId is th Read get_endpoint Get the full JSON of one endpoint, including its targets, auth keys and attributes. Read get_key_policy Returns the project's key policy: defaultKeyTtlDays, maxKeyTtlDays, editorsMayCreateNonExpiringKeys. Read get_line_draft Read one line draft, its optimistic revision, preview, and schedule. Read get_metrics Aggregate request metrics for this project over a time window — volume, error rate and p50/p95/p99 latency, bu Read get_project Get the EchoRelay project this token is scoped to: id, slug, name, caller-facing API base URL, whether the tok Read get_receipts Get every target this request fanned out to, each with its delivery receipt or the reason it has none. A still Read get_request Get one inbound request envelope + every per-target attempt the Consumer made on the way out (success / perman Read get_subscription Get the project owner's current subscription: plan, active flag, period start/end, cancel-at-period-end flag, Read list_active_addons List the project owners currently-active add-ons. Returns [{addonKey, project, monthlyEurCents, activatedAt, n Read list_addons List the optional add-on subscriptions (RPM upgrades, extra team seats, extended log retention, extra file-del Read list_api_keys List the project's inbound API keys (metadata only — the secret plaintext is never returned). Read list_audit_events List project audit-log entries, newest first. Captures who changed what — lines, endpoints, targets, API keys. Read list_config_revisions List retained revisions for one line so a prior revision can be selected for rollback. Read list_credentials List the project's saved credentials — reusable target-auth secrets that can be referenced from any number of Read list_credit_packs List the prepaid credit packs the project owner can purchase. Read-only. Identify a pack to start_topup by its Read list_dlq List entries currently in this project's dead-letter queue, newest first. One inbound request fans out per-tar Read list_endpoints List the endpoints under one line of the project. Read list_lines List the project's versioned API lines (e.g. v1, v2), each with its endpoint count. Read list_members List accepted and pending members of this project. Shows name/email, role, and whether the invite has been acc Read list_project_tokens List the API tokens scoped to a project you own (any holder): id, label, scopes, createdAt, lastUsedAt, expire Read list_projects List the projects on your account (archived included), each with id, slug, name, apiBaseUrl and archived. Requ Read list_requests List inbound API requests the relay has processed for this project, newest first. Hot-tier window is the proje Read list_subscription_plans List the available subscription plans (Free, Pro, Scale) with monthly EUR price, credit allowance, per-project Read preview_plan_change Preview what would happen if change_plan were called with this plan: the immediate-charge amount (cents), the Read reveal_rotation_successor One-shot retrieval of the plaintext for a successor minted by the auto-rotation scheduler (not by rotate_api_k

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

Questions about EchoRelay

Can an AI agent move money through the EchoRelay MCP server? +

Yes. The EchoRelay server exposes 8 financial tools including cancel_subscription, change_plan, downgrade_addon. Without a policy, an autonomous agent can call these with no spend caps, no rate limits, and no approval flow. PolicyLayer lets you block financial tools by default, require human approval, or set per-tool rate limits — enforced on every call.

Can an AI agent delete data through the EchoRelay MCP server? +

Yes. The EchoRelay server exposes 11 destructive tools including cancel_line_publish, delete_credential, delete_endpoint. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through EchoRelay? +

The EchoRelay server has 28 write tools including activate_line, archive_project, config_diff. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach EchoRelay.

How many tools does the EchoRelay MCP server expose? +

78 tools across 4 categories: Destructive, Execute, Read, Write. 29 are read-only. 49 can modify, create, or delete data.

How do I enforce a policy on EchoRelay? +

Register the EchoRelay MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every EchoRelay tool call.

Deterministic rules across all 78 EchoRelay tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Instant setup, no code required.

78 EchoRelay tools catalogued and risk-classified — across an index of 46,500+ MCP servers.

// WHERE THIS COMES FROM

These policies come from EchoRelay's registry record.

The record behind this page: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.