get_endpoint
Get the full JSON of one endpoint, including its targets, auth keys and attributes.
This record as markdown: /tools/dev-echorelay-management/get-endpoint.md
What get_endpoint does on EchoRelay
AI agents call get_endpoint 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". |
endpointId | string | Yes | The endpoint UUID. |
Parameters from the server's own tool schema.
Why get_endpoint is rated Low
This tool queries and returns endpoint configuration data without side effects. While the returned data includes sensitive information (auth keys, attributes), the tool itself performs only read access. No data is created, modified, deleted, or financial operations are involved.
From the tool's definition Tool name 'get_endpoint' and description 'Get the full JSON of one endpoint' indicate a retrieval operation.
Attacks that exploit this kind of access
The rule that runs get_endpoint 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_endpoint, this is the rule to start with:
get_endpoint 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 get_endpoint call is checked against it from then on.
Questions about get_endpoint
Get the full JSON of one endpoint, including its targets, auth keys and attributes. It is categorised as a Read tool in the EchoRelay MCP Server, which means it retrieves data without modifying state.
get_endpoint accepts 2 parameters: lineKey, endpointId. Required: lineKey, endpointId. 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 get_endpoint: 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.
get_endpoint 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 get_endpoint 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 get_endpoint. 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.
get_endpoint 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