Get filtered usage events for specific users and event types
AI agents call cursor_get_usage_events to retrieve information from Sage MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a Read operation—it queries and retrieves usage event data. However, severity is medium rather than low because usage events may contain sensitive information about user behavior, actions, and patterns that could reveal security insights, audit trails, or personal activity details.
From the tool's definition Tool name 'cursor_get_usage_events' and description 'Get filtered usage events for specific users and event types' indicate retrieval of historical usage/audit data without modification.
Documented attack patterns abuse exactly the kind of access cursor_get_usage_events gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Sage MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for cursor_get_usage_events:
{
"version": "1",
"default": "deny",
"tools": {
"cursor_get_usage_events": {}
}
}cursor_get_usage_events is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get filtered usage events for specific users and event types. It is categorised as a Read tool in the Sage MCP MCP Server, which means it retrieves data without modifying state.
Register the Sage MCP server in PolicyLayer and add a rule for cursor_get_usage_events: 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 Sage MCP. Nothing to install.
cursor_get_usage_events 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 cursor_get_usage_events 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 cursor_get_usage_events. 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.
cursor_get_usage_events is provided by the Sage MCP server (sagemcp/sagemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 359 Sage MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
359 Sage MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.