AI agents call copilot_get_usage_by_editor 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 retrieves and aggregates usage metrics—a read-only operation with no side effects. The verb 'get' and the analytical nature of the request (breaking down usage statistics) confirm this is a Read category tool. Severity is low because misuse only exposes usage analytics, which has limited blast radius compared to operational or financial tools.
From the tool's definition Tool name 'copilot_get_usage_by_editor' and description 'Break down Copilot usage by editor/IDE' indicate a query/retrieval operation that returns usage analytics data without modifying any state.
Documented attack patterns abuse exactly the kind of access copilot_get_usage_by_editor 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_usage_by_editor:
{
"version": "1",
"default": "deny",
"tools": {
"copilot_get_usage_by_editor": {}
}
}copilot_get_usage_by_editor 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.
Break down Copilot usage by editor/IDE. 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 copilot_get_usage_by_editor: 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.
copilot_get_usage_by_editor 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 copilot_get_usage_by_editor 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 copilot_get_usage_by_editor. 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.
copilot_get_usage_by_editor 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.