unsubscribe_addon
Cancel an active add-on subscription. Stops future charges; the current cycle stays active until expiry. RPM upgrades are cancelled for THIS project. Returns {addonKey, project, cancelledAt}. Owner-only; requires a token minted with the billing scope.
This record as markdown: /tools/dev-echorelay-management/unsubscribe-addon.md
What unsubscribe_addon does on EchoRelay
AI agents use unsubscribe_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 |
Parameters from the server's own tool schema.
Why unsubscribe_addon is rated Critical
This tool cancels a paid subscription/add-on, directly affecting financial obligations and stopping future charges. It modifies billing state in a way that is at least partially irreversible (cancellation cannot be undone mid-cycle). Financial category takes precedence as it directly commits/removes financial obligations.
From the tool's definition Cancel an active add-on subscription. Stops future charges; RPM upgrades are cancelled for THIS project. Requires a token minted with the billing scope.
Attacks that exploit this kind of access
The rule that runs unsubscribe_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 unsubscribe_addon, this is the rule to start with:
Any call to unsubscribe_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 unsubscribe_addon call is checked against it from then on.
Questions about unsubscribe_addon
Cancel an active add-on subscription. Stops future charges; the current cycle stays active until expiry. RPM upgrades are cancelled for THIS project. Returns {addonKey, project, cancelledAt}. 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.
unsubscribe_addon accepts 1 parameter: addonKey. Required: addonKey. 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 unsubscribe_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.
unsubscribe_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 unsubscribe_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 unsubscribe_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.
unsubscribe_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