windsurf_get_user_analytics
Get per-user analytics for a specific team member over a date range
This record as markdown: /tools/sagemcp-sagemcp/windsurf-get-user-analytics.md
What windsurf_get_user_analytics does on Sage MCP
AI agents call windsurf_get_user_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.
Why windsurf_get_user_analytics is rated Low
This tool queries and retrieves analytics data for a team member over a specified date range. The action is purely informational (Read category) with no capability to modify, delete, or execute operations. The severity is low because analytics data exposure has minimal immediate impact, though confidence is high given the clear read-only intent from both the name and description.
From the tool's definition Tool name contains 'get_' and description states 'Get per-user analytics' — retrieves analytics data with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs windsurf_get_user_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_user_analytics, this is the rule to start with:
windsurf_get_user_analytics is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Sage MCP, apply this rule, and every windsurf_get_user_analytics call is checked against it from then on.
Questions about windsurf_get_user_analytics
Get per-user analytics for a specific team member 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.
Register the Sage MCP server in PolicyLayer and add a rule for windsurf_get_user_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.
windsurf_get_user_analytics 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 windsurf_get_user_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.
Set action: deny in the PolicyLayer policy for windsurf_get_user_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.
windsurf_get_user_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.
More on Sage, and thousands of servers like it.
This server
Across the catalogue