Low Risk

copilot_get_legacy_metrics

Get legacy Copilot metrics (deprecated endpoint, use org usage for new integrations)

How to control copilot_get_legacy_metrics ↓

AI agents call copilot_get_legacy_metrics 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 historical/legacy metrics data with no side effects. The 'get' operation and the nature of metric retrieval (querying past data) clearly indicate a Read operation. Severity is low because metrics are typically non-sensitive operational data, and the endpoint is deprecated so its impact is further reduced.

From the tool's definition Tool name contains 'get' and description explicitly states it retrieves 'legacy Copilot metrics' from a deprecated endpoint. No modification, deletion, execution, or financial operations are described.

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

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

copilot_get_legacy_metrics 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 copilot_get_legacy_metrics tool do? +

Get legacy Copilot metrics (deprecated endpoint, use org usage for new integrations). 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_legacy_metrics? +

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

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

Can I rate-limit copilot_get_legacy_metrics? +

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

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

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