Counts: total/production conversations, events, connector calls, top-5 connectors, date range.
AI agents call get_summary_stats to retrieve information from Copilot Insights MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs aggregation and retrieval of telemetry metrics from existing data. It queries counts and statistics without creating, modifying, deleting, or executing any operations. No side effects, financial impact, or irreversible actions are possible.
From the tool's definition Tool retrieves summary statistics and counts (total conversations, events, connector calls, top connectors, date range) with no modification operations. Name 'get_summary_stats' and description indicate data querying only.
Attacks that exploit this kind of access
Counts: total/production conversations, events, connector calls, top-5 connectors, date range. It is categorised as a Read tool in the Copilot Insights MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Copilot Insights MCP Server MCP server in PolicyLayer and add a rule for get_summary_stats: 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 Copilot Insights MCP Server. Nothing to install.
get_summary_stats 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 get_summary_stats 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 get_summary_stats. 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.
get_summary_stats is provided by the Copilot Insights MCP Server MCP server (syokiel/copilot-insights). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →