List all available Microsoft Graph API resource categories with descriptions and load status. Categories: users (Azure AD/Entra ID), files (OneDrive/SharePoint drives), mail (Exchange Online), calendar (Outlook), groups (M365/security groups), notes (OneNote), tasks (Planner/To Do), sites (ShareP...
AI agents call list_categories to retrieve information from Ms Graph Dev without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and lists available API categories and their metadata. It performs no mutations, executions, or destructive operations. It is informational only, supporting users in understanding what Graph API resources are available. The blast radius of misuse is minimal—an attacker could only enumerate what categories exist, which is public metadata about the API surface.
From the tool's definition Tool name 'list_categories' and description stating it 'List all available Microsoft Graph API resource categories with descriptions and load status'—a pure enumeration/metadata operation with no side effects.
Attacks that exploit this kind of access
List all available Microsoft Graph API resource categories with descriptions and load status. Categories: users (Azure AD/Entra ID), files (OneDrive/SharePoint drives), mail (Exchange Online), calendar (Outlook), groups (M365/security groups), notes (OneNote), tasks (Planner/To Do), sites (SharePoint sites and lists), subscriptions (webhooks/change notifications). It is categorised as a Read tool in the Ms Graph Dev MCP Server, which means it retrieves data without modifying state.
Register the Ms Graph Dev MCP server in PolicyLayer and add a rule for list_categories: 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 Ms Graph Dev. Nothing to install.
list_categories 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 list_categories 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 list_categories. 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.
list_categories is provided by the Ms Graph Dev MCP server (stubbedev/ms-graph-dev-mcp). 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 →