get_user_deep_dive

Deep dive into a specific user

Server Cursor Usage ofershap/cursor-usage
Category Read
Risk class Low
Parameters 00 required

What get_user_deep_dive does on Cursor Usage

AI agents call get_user_deep_dive 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.

Why get_user_deep_dive needs a policy

This tool queries and retrieves user-level analytics and usage information without modifying, deleting, or executing any external operations. It is a passive data retrieval operation with no side effects or capability to alter system state. The low severity reflects that misuse would expose analytics/usage data but poses no direct operational, financial, or destructive risk.

From the tool's definition Tool name contains 'get_' prefix and description states 'Deep dive into a specific user' — retrieves detailed user analytics data.

Questions about get_user_deep_dive

What does the get_user_deep_dive tool do? +

Deep dive into a specific user. It is categorised as a Read tool in the Cursor Usage MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_user_deep_dive? +

Register the Cursor Usage MCP server in PolicyLayer and add a rule for get_user_deep_dive: 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.

What risk level is get_user_deep_dive? +

get_user_deep_dive is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_user_deep_dive? +

Yes. Add a rate_limit block to the get_user_deep_dive 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.

How do I block get_user_deep_dive completely? +

Set action: deny in the PolicyLayer policy for get_user_deep_dive. 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.

What MCP server provides get_user_deep_dive? +

get_user_deep_dive 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.