update_credential

SERVEREchoRelay SOURCEhttps://mcp.echorelay.dev

Medium RISK CLASS

Category Write

Parameters 41 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-credential.md

WHAT IT DOES

What update_credential does on EchoRelay

AI agents use update_credential 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
`auth`	object	—	Same shape as create_credential. Omit to keep the existing auth entirely.
`name`	string	—	New name. Omit to keep the existing one.
`credentialId`	string	Yes	UUID of the credential (from list_credentials).
`destinationHost`	string	—	Permanent — may only restate the credential's current host (omit it, or send back what list_credentials reported). Any other value is refused; a credential is n

Parameters from the server's own tool schema.

RISK

Why update_credential is rated Medium

An AI agent can call update_credential 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 signalsHandles credentials or secrets (auth) · Bulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

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

update_credential Rate-limited

update_credential 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_credential": {
      "limits": [
        {
          "counter": "update_credential_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_credential call is checked against it from then on.

FAQ

Questions about update_credential

What does the update_credential tool do? +

Rename a credential and/or rotate its secret, publishing the change immediately so every target that uses this credential picks it up right away. Omit a secret field (or the whole auth object) to keep the existing value — the vault can never show a secret back to confirm it, so leaving it out means "unchanged," not "cleared." The destination host cannot be changed here: create a new credential for a new destination. 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_credential accept? +

update_credential accepts 4 parameters: auth, name, credentialId, destinationHost. Required: credentialId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on update_credential? +

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

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

Can I rate-limit update_credential? +

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

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

update_credential 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 →