get_billing
Get the project's credit balances (paid + testing). Check this first when a 402 (out of credits) or 429 (rate-limited) is unexpected — it is the project's billing-state oracle.
This record as markdown: /tools/dev-echorelay-management/get-billing.md
What get_billing does on EchoRelay
AI agents call get_billing to retrieve information from EchoRelay without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_billing is rated Low
This tool performs a read-only query of billing information. It retrieves current credit balances and billing status to help diagnose rate-limiting or credit issues. While billing information is sensitive business data, reading it poses minimal risk compared to tools that can modify billing state (e.g., change_plan, cancel_subscription visible in sibling tools).
From the tool's definition Tool retrieves project credit balances and billing state without modifying data. Description states 'Get the project's credit balances' and 'is the project's billing-state oracle' — purely informational queries.
Attacks that exploit this kind of access
The rule that runs get_billing 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 get_billing, this is the rule to start with:
get_billing is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect EchoRelay, apply this rule, and every get_billing call is checked against it from then on.
Questions about get_billing
Get the project's credit balances (paid + testing). Check this first when a 402 (out of credits) or 429 (rate-limited) is unexpected — it is the project's billing-state oracle. It is categorised as a Read tool in the EchoRelay MCP Server, which means it retrieves data without modifying state.
Register the EchoRelay MCP server in PolicyLayer and add a rule for get_billing: 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.
get_billing is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_billing 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 get_billing. 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.
get_billing 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.
This server
Across the catalogue