Count people matching filters in Microsoft Graph directory data. Returns only the count, not the full results.
AI agents call count_people to retrieve information from M365connector without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves summary information (counts) from a directory without any side effects. It does not create, modify, delete, or execute operations. The read-only nature and non-sensitive aggregated output (count only, not full results) make this a straightforward Read category with low severity.
From the tool's definition Tool description states it 'Count people matching filters in Microsoft Graph directory data. Returns only the count, not the full results.' The operation is read-only: it queries directory data and returns aggregated counts without modifying any data.
Attacks that exploit this kind of access
Count people matching filters in Microsoft Graph directory data. Returns only the count, not the full results. It is categorised as a Read tool in the M365connector MCP Server, which means it retrieves data without modifying state.
Register the M365connector MCP server in PolicyLayer and add a rule for count_people: 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 M365connector. Nothing to install.
count_people 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 count_people 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 count_people. 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.
count_people is provided by the M365connector MCP server (m365connector). 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 →