Get billing groups with member lists, group-level spend, and daily spend breakdown. Also returns billing cycle dates.
AI agents call get_billing_groups to retrieve information from Cursor Usage without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries billing and spending data without modifying, deleting, or executing actions. It falls squarely in the Read category. Severity is medium rather than low because the data returned (spend, costs, billing cycles, member lists) could inform financial decisions and reveals sensitive financial information, making misuse or unauthorized access a moderate risk in an AI agent context.
From the tool's definition Tool name 'get_billing_groups' and description 'Get billing groups with member lists, group-level spend, and daily spend breakdown' indicate data retrieval only.
Attacks that exploit this kind of access
Get billing groups with member lists, group-level spend, and daily spend breakdown. Also returns billing cycle dates. It is categorised as a Read tool in the Cursor Usage MCP Server, which means it retrieves data without modifying state.
Register the Cursor Usage MCP server in PolicyLayer and add a rule for get_billing_groups: 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 Cursor Usage. Nothing to install.
get_billing_groups 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_groups 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_groups. 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_groups is provided by the Cursor Usage MCP server (ofershap/cursor-usage). 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 →