Get current billing cycle spending for all team members. Shows spend in dollars, included vs overage, fast premium requests, and spend limits.
AI agents call get_spending 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 displays spending information (dollars, included vs overage, fast premium requests, spend limits) but does not move money, process payments, or commit financial obligations. It is strictly a read operation on billing analytics. While the data concerns finances, the tool itself performs no financial transaction or obligation.
From the tool's definition Tool is named 'get_spending' and described as 'Get current billing cycle spending' — uses read-only verb 'Get' to retrieve financial data without modifying it.
Attacks that exploit this kind of access
Get current billing cycle spending for all team members. Shows spend in dollars, included vs overage, fast premium requests, and spend limits. 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_spending: 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_spending 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_spending 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_spending. 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_spending 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 →