Per-user Viva Insights weekly hours (focus, meetings, chat, email). Filter by user_id or week_start.
AI agents call get_viva_insights 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 queries telemetry data about user activity (focus time, meetings, chat, email patterns) from Microsoft Viva Insights. It has no write, execute, or destructive capabilities—it only reads and returns aggregated metrics.
From the tool's definition Tool description explicitly states it retrieves 'per-user Viva Insights weekly hours' with filtering capabilities. The verbs 'get' and the parameters (user_id, week_start) indicate data querying with no modification or deletion.
Attacks that exploit this kind of access
Per-user Viva Insights weekly hours (focus, meetings, chat, email). Filter by user_id or week_start. 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_viva_insights: 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_viva_insights 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_viva_insights 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_viva_insights. 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_viva_insights 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 →