delete_credential
Delete a saved credential. Blocked (not a permission or not-found error — a validation error) while any target still references it; repoint or remove those targets first.
This record as markdown: /tools/dev-echorelay-management/delete-credential.md
What delete_credential does on EchoRelay
AI agents call delete_credential to permanently remove resources in EchoRelay, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
credentialId | string | Yes | UUID of the credential to delete. |
Parameters from the server's own tool schema.
Why delete_credential is rated Critical
This tool permanently removes a saved credential from the system. Although the tool includes safeguards (blocking deletion if targets still reference it), the core action is irreversible data destruction. Destructive is the most severe category and takes precedence over Write.
From the tool's definition Tool name is 'delete_credential' and description explicitly states 'Delete a saved credential'. The term 'Delete' combined with the irreversible nature of removing a credential makes this destructive.
Attacks that exploit this kind of access
The rule that runs delete_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 delete_credential, this is the rule to start with:
delete_credential is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect EchoRelay, apply this rule, and every delete_credential call is checked against it from then on.
Questions about delete_credential
Delete a saved credential. Blocked (not a permission or not-found error — a validation error) while any target still references it; repoint or remove those targets first. It is categorised as a Destructive tool in the EchoRelay MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
delete_credential accepts 1 parameter: credentialId. Required: credentialId. 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 delete_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.
delete_credential is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_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.
Set action: deny in the PolicyLayer policy for delete_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.
delete_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.
More on EchoRelay, and thousands of servers like it.
Across the catalogue