Get team tab/autocomplete usage analytics for a date range
AI agents call cursor_get_tab_usage 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 tool retrieves analytics and usage data for a specified date range without side effects. It performs a simple query operation to fetch pre-computed or aggregated metrics about team autocomplete feature usage. No data is modified, deleted, or any external operations triggered. This is a straightforward read operation with minimal blast radius if misused by an AI agent.
From the tool's definition Tool name and description indicate retrieval of analytics data: 'Get team tab/autocomplete usage analytics for a date range' - uses 'Get' verb and describes querying usage metrics, with no mention of modification, deletion, or execution capabilities.
Documented attack patterns abuse exactly the kind of access cursor_get_tab_usage 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_tab_usage:
{
"version": "1",
"default": "deny",
"tools": {
"cursor_get_tab_usage": {}
}
}cursor_get_tab_usage 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 team tab/autocomplete usage analytics for a date range. 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_tab_usage: 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_tab_usage 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_tab_usage 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_tab_usage. 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_tab_usage 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.