Get a comprehensive team overview: member count, total spend, top spenders, DAU, and most-used models. This is the best starting point for understanding your team
AI agents call get_team_overview 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 aggregates billing and usage analytics metadata. While it exposes spend information (a sensitive metric), it performs no side effects, modifications, or financial transactions. The blast radius is limited to information disclosure; an AI agent cannot directly incur costs or modify financial systems through this read-only query.
From the tool's definition Tool name 'get_team_overview' and description 'Get a comprehensive team overview' indicates a retrieval operation.
Attacks that exploit this kind of access
Get a comprehensive team overview: member count, total spend, top spenders, DAU, and most-used models. This is the best starting point for understanding your team. 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_team_overview: 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_team_overview 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_team_overview 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_team_overview. 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_team_overview 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 →