Analyze code statistics across all conversations
AI agents call analyze_code_statistics to retrieve information from Cursor DB MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and performs analytical computations on conversation data to generate statistics. It does not create, modify, delete, execute code, or commit financial actions. The operation has no side effects beyond reading conversation history stored in the SQLite database.
From the tool's definition Tool name 'analyze_code_statistics' combined with server description stating 'querying, searching, and analyzing Cursor IDE conversation history' indicates data retrieval and analysis without modification.
Attacks that exploit this kind of access
Analyze code statistics across all conversations. It is categorised as a Read tool in the Cursor DB MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Cursor DB MCP Server MCP server in PolicyLayer and add a rule for analyze_code_statistics: 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 DB MCP Server. Nothing to install.
analyze_code_statistics 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 analyze_code_statistics 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 analyze_code_statistics. 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.
analyze_code_statistics is provided by the Cursor DB MCP Server MCP server (taylorchen/cursor-db-mcp). 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 →