update_endpoint

Update an endpoint immediately or in its line draft. The patch is merged field-by-field. Requires edit access.

SERVEREchoRelay SOURCEhttps://mcp.echorelay.dev

Medium RISK CLASS

Category Write

Parameters 63 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/dev-echorelay-management/update-endpoint.md

WHAT IT DOES

What update_endpoint does on EchoRelay

AI agents use update_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
`patch`	object	Yes	Partial endpoint document — same shape as create_endpoint, every field optional.
`lineKey`	string	Yes	The line key.
`commitMode`	string	—	Defaults to publish. Draft writes require draftRevision.
`endpointId`	string	Yes	The endpoint UUID.
`scheduledAt`	string	—	Compatibility alias: stage this update then schedule its line.
`draftRevision`	integer	—	Current line draft revision, required for draft writes.

Parameters from the server's own tool schema.

RISK

Why update_endpoint is rated Medium

An AI agent can call update_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 (patch.url) · Handles credentials or secrets (patch.targets[].auth) · Accepts raw HTML/template content (patch.targets[].mapping[].template) · High parameter count (57 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

update_endpoint Rate-limited

update_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_endpoint": {
      "limits": [
        {
          "counter": "update_endpoint_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect EchoRelay, apply this rule, and every update_endpoint call is checked against it from then on.

FAQ

Questions about update_endpoint

What does the update_endpoint tool do? +

Update an endpoint immediately or in its line draft. The patch is merged field-by-field. 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.

What parameters does update_endpoint accept? +

update_endpoint accepts 6 parameters: patch, lineKey, commitMode, endpointId, scheduledAt, draftRevision. Required: patch, lineKey, endpointId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on update_endpoint? +

Register the EchoRelay MCP server in PolicyLayer and add a rule for update_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.

What risk level is update_endpoint? +

update_endpoint is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_endpoint? +

Yes. Add a rate_limit block to the update_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.

How do I block update_endpoint completely? +

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

What MCP server provides update_endpoint? +

update_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.

KEEP EXPLORING

More on EchoRelay, and thousands of servers like it.

This server

All 78 EchoRelay tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP →team_manager_update_budget on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →