Get daily usage data per user: lines added/deleted, applies, accepts, rejects, tabs, requests by mode (composer/chat/agent), models used, and client versions.
AI agents call get_daily_usage 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 historical usage analytics and metrics without side effects. It queries pre-computed or logged data about user behavior and system activity. Even though the data could be sensitive (usage patterns, spend), the tool itself performs only read operations with no capability to modify, delete, or execute external systems. The blast radius of misuse is limited to information disclosure.
From the tool's definition Tool name 'get_daily_usage' and description 'Get daily usage data' indicate retrieval of analytics data. No modification, deletion, or execution capability described.
Attacks that exploit this kind of access
Get daily usage data per user: lines added/deleted, applies, accepts, rejects, tabs, requests by mode (composer/chat/agent), models used, and client versions. 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_daily_usage: 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_daily_usage 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_daily_usage 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_daily_usage. 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_daily_usage 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 →