Get top file extensions being edited with AI: which file types get the most AI suggestions, accepts, and rejects.
AI agents call get_file_extensions 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 analytics data about which file extensions are most frequently edited with AI assistance. It has no side effects, does not modify or delete data, does not execute code, and does not involve financial transactions. It is a straightforward read-only retrieval of usage statistics, making it a clear Read category risk with low severity since it only exposes aggregated usage metadata.
From the tool's definition Tool name is 'get_file_extensions' and description states 'Get top file extensions being edited with AI' — purely a retrieval/query operation with no modification, deletion, or execution capability. Returns analytics data about file type usage.
Attacks that exploit this kind of access
Get top file extensions being edited with AI: which file types get the most AI suggestions, accepts, and rejects. 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_file_extensions: 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_file_extensions 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_file_extensions 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_file_extensions. 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_file_extensions 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 →