Retrieve billing history
AI agents call get_billing_history to retrieve information from VoIPBin MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves billing data without modifying, deleting, or executing actions. It is clearly a Read operation. Severity is elevated to medium rather than low because billing history is sensitive financial information that could be misused if an AI agent inappropriately accesses or exfiltrates a user's billing records, even though the tool itself performs no financial transactions or destructive actions.
From the tool's definition Tool name is 'get_billing_history' and description states 'Retrieve billing history' — a query operation with no side effects.
Attacks that exploit this kind of access
Retrieve billing history. It is categorised as a Read tool in the VoIPBin MCP Server MCP Server, which means it retrieves data without modifying state.
Register the VoIPBin MCP Server MCP server in PolicyLayer and add a rule for get_billing_history: 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 VoIPBin MCP Server. Nothing to install.
get_billing_history 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_history 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_history. 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_history is provided by the VoIPBin MCP Server MCP server (nrjchnd/voipbin-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →