Explain Microsoft Graph permission types — delegated vs application, how to register an app, and least-privilege best practices.
AI agents call graph_explain_permissions 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 presents documentation/explanation about Microsoft Graph permission types and registration practices. It has no side effects, does not execute code, modify data, or trigger external operations. It is a pure Read operation that provides reference material to help users understand permission models.
From the tool's definition Tool name and description indicate it 'Explain[s]' and provides 'how to register an app, and least-privilege best practices' — this is purely informational and educational about permission concepts, not executing, modifying, or accessing any actual data or…
Attacks that exploit this kind of access
Explain Microsoft Graph permission types — delegated vs application, how to register an app, and least-privilege best practices. 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 graph_explain_permissions: 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.
graph_explain_permissions 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 graph_explain_permissions 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 graph_explain_permissions. 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.
graph_explain_permissions 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 →