default_endpoint_template
Return a canonical minimal-valid endpoint JSON for a fresh line. POST it verbatim to create_endpoint to land an immediately-working mock endpoint, then customise. Read-only.
This record as markdown: /tools/dev-echorelay-management/default-endpoint-template.md
What default_endpoint_template does on EchoRelay
AI agents call default_endpoint_template 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.
Why default_endpoint_template is rated Low
This tool retrieves and returns template/reference data without modifying any state. It is a template generator for documentation/schema purposes, not an operation that creates, executes, or modifies actual endpoint configurations. The explicit 'Read-only' designation confirms the Read category with low severity since it has no blast radius beyond information disclosure of a template structure.
From the tool's definition Tool description explicitly states 'Read-only' and the function returns 'a canonical minimal-valid endpoint JSON' template. The verb 'Return' indicates data retrieval with no side effects.
Attacks that exploit this kind of access
The rule that runs default_endpoint_template 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 default_endpoint_template, this is the rule to start with:
default_endpoint_template is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect EchoRelay, apply this rule, and every default_endpoint_template call is checked against it from then on.
Questions about default_endpoint_template
Return a canonical minimal-valid endpoint JSON for a fresh line. POST it verbatim to create_endpoint to land an immediately-working mock endpoint, then customise. Read-only. It is categorised as a Read tool in the EchoRelay MCP Server, which means it retrieves data without modifying state.
default_endpoint_template accepts 1 parameter: lineKey. Required: lineKey. The full parameter table on this page comes from the server's own tool schema.
Register the EchoRelay MCP server in PolicyLayer and add a rule for default_endpoint_template: 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.
default_endpoint_template is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the default_endpoint_template 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.
Set action: deny in the PolicyLayer policy for default_endpoint_template. 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.
default_endpoint_template 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.
More on EchoRelay, and thousands of servers like it.
This server
Across the catalogue