get_billing
Get the project's credit balances (paid + testing) and which ledger it settles on. billingModel is prepaid (metered against the credit balance) or invoiceable (an Enterprise account, settled on the contract — its credit fields read empty/zero by design, not because it is out of credits). A zero b...
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
Even though get_billing only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
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) and which ledger it settles on. billingModel is prepaid (metered against the credit balance) or invoiceable (an Enterprise account, settled on the contract — its credit fields read empty/zero by design, not because it is out of credits). A zero balance is not on its own a reason to stop: live traffic is never refused for an empty balance, and a free-tier project is exempt from live credit billing entirely. Only the testing pool refuses when exhausted (402 testing_credits_exhausted). Read this before concluding from any other field that a project cannot send. 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