Get daily active users over time, including breakdowns for CLI, cloud agent, and Bugbot usage.
AI agents call get_dau 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 analytics data about daily active user counts across different client types (CLI, cloud agent, Bugbot). It performs no mutations, deletions, financial transactions, or code execution. The data retrieved is for monitoring and analysis purposes only. As a read operation with minimal blast radius if misused, it merits low severity.
From the tool's definition Tool name 'get_dau' and description 'Get daily active users over time' indicate a retrieval operation. The verb 'Get' and the context of 'analytics' and 'track' confirm this is a read-only query for usage metrics with no side effects.
Attacks that exploit this kind of access
Get daily active users over time, including breakdowns for CLI, cloud agent, and Bugbot usage. 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_dau: 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_dau 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_dau 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_dau. 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_dau 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 →