downgrade_addon
Schedule a tier downgrade for a non-stackable add-on (RPM tier). The current tier stays active until nextRenewalAt; at that point the lower tier is charged and activated. No mid-cycle charge. Use list_addons to find available keys. Returns {addonKey, targetAddonKey, project, effectiveAt}. Owner-o...
This record as markdown: /tools/dev-echorelay-management/downgrade-addon.md
What downgrade_addon does on EchoRelay
AI agents use downgrade_addon to commit financial operations through EchoRelay, usually the final step of a payment, billing, or trading workflow. A call moves real money.
| Parameter | Type | Required | Description |
|---|---|---|---|
addonKey | string | Yes | Current active add-on key to downgrade from. |
targetAddonKey | string | Yes | Target (lower) add-on key to downgrade to. |
Parameters from the server's own tool schema.
Why downgrade_addon is rated Critical
This tool modifies a financial subscription/billing plan by scheduling a tier downgrade for a paid add-on. It directly affects billing obligations (what tier is charged at next renewal), placing it firmly in the Financial category. Misuse could result in unintended service tier changes affecting revenue or service levels.
From the tool's definition 'Schedule a tier downgrade for a non-stackable add-on (RPM tier)... the lower tier is charged and activated... No mid-cycle charge... requires a token minted with the billing scope'
Attacks that exploit this kind of access
The rule that runs downgrade_addon 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 downgrade_addon, this is the rule to start with:
Any call to downgrade_addon is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect EchoRelay, apply this rule, and every downgrade_addon call is checked against it from then on.
Questions about downgrade_addon
Schedule a tier downgrade for a non-stackable add-on (RPM tier). The current tier stays active until nextRenewalAt; at that point the lower tier is charged and activated. No mid-cycle charge. Use list_addons to find available keys. Returns {addonKey, targetAddonKey, project, effectiveAt}. Owner-only; requires a token minted with the billing scope. It is categorised as a Financial tool in the EchoRelay MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
downgrade_addon accepts 2 parameters: addonKey, targetAddonKey. Required: addonKey, targetAddonKey. 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 downgrade_addon: 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.
downgrade_addon is a Financial 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 downgrade_addon 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 downgrade_addon. 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.
downgrade_addon 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