get_config

Get the project's full relay configuration — the exact JSON the EchoRelay Framework consumes for this tenant.

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/get-config.md

WHAT IT DOES

What get_config does on EchoRelay

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

This tool retrieves and queries configuration data without modifying, deleting, or executing operations. It has no side effects beyond reading. While the configuration data returned might be sensitive (e.g., containing endpoint details, key references), the tool itself is a passive read operation.

From the tool's definition Tool name is 'get_config' with description stating 'Get the project's full relay configuration'. The verb 'Get' and the read-only nature of retrieving configuration without modification confirms this is a retrieval operation.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

get_config Allowed

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

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

FAQ

Questions about get_config

What does the get_config tool do? +

Get the project's full relay configuration — the exact JSON the EchoRelay Framework consumes for this tenant. 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 get_config? +

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

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

Can I rate-limit get_config? +

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

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

get_config 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 64 EchoRelay tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →