create_endpoint
Create an endpoint under a line. Defaults to immediate publish; draft mode requires draftRevision. scheduledAt stages the line draft then schedules it. Requires edit access.
This record as markdown: /tools/dev-echorelay-management/create-endpoint.md
What create_endpoint does on EchoRelay
AI agents use create_endpoint to create or update resources in EchoRelay, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your EchoRelay environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
lineKey | string | Yes | The line key to create the endpoint under. |
endpoint | object | Yes | An EchoRelay endpoint. Round-trips with the JSON returned by get_endpoint. |
commitMode | string | — | Defaults to publish. Draft writes require draftRevision. |
scheduledAt | string | — | Compatibility alias: stage this endpoint in its line draft then schedule that line. |
draftRevision | integer | — | Current line draft revision, required for draft writes. |
Parameters from the server's own tool schema.
Why create_endpoint is rated Medium
An AI agent can call create_endpoint faster than any human can review: one bad instruction and it creates or modifies resources in EchoRelay by the hundred, each call as confident as the last.
Risk signalsAccepts URL/endpoint input (endpoint) · Handles credentials or secrets (endpoint.targets[].auth) · Accepts raw HTML/template content (endpoint.targets[].mapping[].template) · High parameter count (56 properties)
Attacks that exploit this kind of access
The rule that runs create_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 create_endpoint, this is the rule to start with:
create_endpoint stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 create_endpoint call is checked against it from then on.
Questions about create_endpoint
Create an endpoint under a line. Defaults to immediate publish; draft mode requires draftRevision. scheduledAt stages the line draft then schedules it. Requires edit access. It is categorised as a Write tool in the EchoRelay MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
create_endpoint accepts 5 parameters: lineKey, endpoint, commitMode, scheduledAt, draftRevision. Required: lineKey, endpoint. 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 create_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.
create_endpoint is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_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 create_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.
create_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