Get detailed usage and billing report for your account
AI agents call get_usage_report to retrieve information from MoluAbi MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves and queries usage and billing data. It does not create, modify, delete, execute code, or commit financial transactions. While the data returned may be sensitive (billing information), the tool itself is read-only and non-destructive. The low severity reflects that unauthorized access would be a data exposure risk rather than a capability to cause direct harm through the tool itself.
From the tool's definition Tool name is 'get_usage_report' and description states 'Get detailed usage and billing report for your account' — this is a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Get detailed usage and billing report for your account. It is categorised as a Read tool in the MoluAbi MCP Server MCP Server, which means it retrieves data without modifying state.
Register the MoluAbi MCP Server MCP server in PolicyLayer and add a rule for get_usage_report: 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 MoluAbi MCP Server. Nothing to install.
get_usage_report 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_usage_report 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_usage_report. 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_usage_report is provided by the MoluAbi MCP Server MCP server (oregpt/moluabi-mcp-server). 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 →