Low Risk

cursor_get_leaderboard

Get team usage leaderboard for a date range

How to control cursor_get_leaderboard ↓

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

Low Risk

This tool retrieves team usage statistics for display purposes. It has no side effects, does not modify data, execute code, delete information, or move money. The blast radius of misuse is minimal—an attacker could view team usage metrics but cannot alter systems or data. Classified as Read with low severity.

From the tool's definition Tool description states 'Get team usage leaderboard for a date range' — a retrieval operation with no modification, deletion, or execution of code. The verb 'Get' and the nature of querying leaderboard data indicate a read-only query.

Documented attack patterns abuse exactly the kind of access cursor_get_leaderboard 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_leaderboard:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "cursor_get_leaderboard": {}
  }
}

cursor_get_leaderboard is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Sage MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the cursor_get_leaderboard tool do? +

Get team usage leaderboard 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.

How do I enforce a policy on cursor_get_leaderboard? +

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

What risk level is cursor_get_leaderboard? +

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

Can I rate-limit cursor_get_leaderboard? +

Yes. Add a rate_limit block to the cursor_get_leaderboard 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 cursor_get_leaderboard completely? +

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

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

Enforce policy on every Sage MCP tool call.

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.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.