windsurf_get_analytics

Get team-wide analytics for Windsurf/Codeium usage over a date range

SERVERSage MCP SOURCEsagemcp/sagemcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/sagemcp-sagemcp/windsurf-get-analytics.md

WHAT IT DOES

What windsurf_get_analytics does on Sage MCP

AI agents call windsurf_get_analytics to retrieve information from Sage MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why windsurf_get_analytics is rated Low

This tool retrieves analytics data (a read operation) but accesses team-wide usage information which could be considered sensitive business intelligence. While categorically a Read operation, the sensitivity of team analytics data and potential for misuse to understand usage patterns warrants medium severity. The tool does not create, modify, delete, or execute code; it only queries and returns data.

From the tool's definition Tool name contains 'get_analytics' and description states 'Get team-wide analytics for Windsurf/Codeium usage' — this is a retrieval/query operation with no modification or deletion of data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs windsurf_get_analytics safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Sage MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For windsurf_get_analytics, this is the rule to start with:

windsurf_get_analytics Allowed

windsurf_get_analytics is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "windsurf_get_analytics": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Sage MCP, apply this rule, and every windsurf_get_analytics call is checked against it from then on.

FAQ

Questions about windsurf_get_analytics

What does the windsurf_get_analytics tool do? +

Get team-wide analytics for Windsurf/Codeium usage over 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 windsurf_get_analytics? +

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

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

Can I rate-limit windsurf_get_analytics? +

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

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

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

KEEP EXPLORING

More on Sage, and thousands of servers like it.

This server

All 359 Sage tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →