copilot_get_usage_trends

Get 28-day rolling usage trends for an organization

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/copilot-get-usage-trends.md

WHAT IT DOES

What copilot_get_usage_trends does on Sage MCP

AI agents call copilot_get_usage_trends 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 copilot_get_usage_trends is rated Low

This is a read-only query operation that retrieves aggregated usage trend data for an organization. No data is modified, deleted, executed, or created. The 28-day rolling window is a standard analytics query pattern. Even though it provides organizational metrics (potentially sensitive), the action itself is passive retrieval only.

From the tool's definition Tool name contains 'get' and description states 'Get 28-day rolling usage trends' — retrieves historical usage metrics with no side effects or state changes.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs copilot_get_usage_trends 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 copilot_get_usage_trends, this is the rule to start with:

copilot_get_usage_trends Allowed

copilot_get_usage_trends 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": {
    "copilot_get_usage_trends": {}
  }
}

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 copilot_get_usage_trends call is checked against it from then on.

FAQ

Questions about copilot_get_usage_trends

What does the copilot_get_usage_trends tool do? +

Get 28-day rolling usage trends for an organization. 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 copilot_get_usage_trends? +

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

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

Can I rate-limit copilot_get_usage_trends? +

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

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

copilot_get_usage_trends 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 →