start_topup
Begin a credit-pack top-up for the project owner. Pass the packs eurCents (from list_credit_packs). Returns {checkoutUrl, credits, eurCents, directCharge} or {transactionId, credits, eurCents, directCharge:true} on subsequent MCP purchases. Owner-only; requires a token minted with the billing scope.
This record as markdown: /tools/dev-echorelay-management/start-topup.md
What start_topup does on EchoRelay
AI agents use start_topup 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 |
|---|---|---|---|
eurCents | integer | Yes | Pack price in EUR cents, matching a pack returned by list_credit_packs. |
Parameters from the server's own tool schema.
Why start_topup is rated Critical
This tool initiates a financial transaction — purchasing a credit pack denominated in euros. It can result in immediate charges (directCharge:true) to the owner's payment method. This is unambiguously a Financial category action with critical severity since an AI agent misusing this could trigger unauthorized monetary charges.
From the tool's definition Begin a credit-pack top-up for the project owner... eurCents... directCharge... billing scope
Attacks that exploit this kind of access
The rule that runs start_topup 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 start_topup, this is the rule to start with:
Any call to start_topup 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 start_topup call is checked against it from then on.
Questions about start_topup
Begin a credit-pack top-up for the project owner. Pass the packs eurCents (from list_credit_packs). Returns {checkoutUrl, credits, eurCents, directCharge} or {transactionId, credits, eurCents, directCharge:true} on subsequent MCP purchases. 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.
start_topup accepts 1 parameter: eurCents. Required: eurCents. 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 start_topup: 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.
start_topup 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 start_topup 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 start_topup. 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.
start_topup 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