Get MCP (Model Context Protocol) adoption analytics for a date range
AI agents call cursor_get_mcp_adoption 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 queries and returns adoption analytics metrics for a specified date range. It is a pure read operation with no side effects, no data modification, no code execution, and no irreversible actions. The analytics data returned poses minimal security risk even if accessed by an unauthorized party, as adoption metrics are typically non-sensitive business intelligence.
From the tool's definition Tool name includes 'get' (read operation) and description states 'Get MCP adoption analytics' — retrieves analytics data without modifying, creating, deleting, or executing external operations.
Documented attack patterns abuse exactly the kind of access cursor_get_mcp_adoption 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_mcp_adoption:
{
"version": "1",
"default": "deny",
"tools": {
"cursor_get_mcp_adoption": {}
}
}cursor_get_mcp_adoption 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 MCP (Model Context Protocol) adoption 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_mcp_adoption: 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_mcp_adoption 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_mcp_adoption 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_mcp_adoption. 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_mcp_adoption 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.