Acts as a versatile assistant to call any Microsoft Graph or Azure Resource Management API endpoint. Use this for managing users, groups, applications, devices, policies (Conditional Access, Intune Configuration/Compliance), security alerts, audit logs, SharePoint, Exchange, and more.
AI agents invoke Dynamicendpoint_automation_assistant to trigger actions in Microsoft 365 Core MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool can invoke arbitrary Graph API and Azure Resource Management endpoints, meaning it can perform Read, Write, Destructive, and potentially Financial operations depending on arguments. Per the rules, the most severe applicable category is chosen.
From the tool's definition 'Acts as a versatile assistant to call any Microsoft Graph or Azure Resource Management API endpoint' — unrestricted access to 1000+ endpoints covering users, groups, applications, devices, policies, security alerts, audit logs, SharePoint, Exchange, and more.
Attacks that exploit this kind of access
Acts as a versatile assistant to call any Microsoft Graph or Azure Resource Management API endpoint. Use this for managing users, groups, applications, devices, policies (Conditional Access, Intune Configuration/Compliance), security alerts, audit logs, SharePoint, Exchange, and more. It is categorised as a Execute tool in the Microsoft 365 Core MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Microsoft 365 Core MCP Server MCP server in PolicyLayer and add a rule for Dynamicendpoint_automation_assistant: 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 Microsoft 365 Core MCP Server. Nothing to install.
Dynamicendpoint_automation_assistant is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the Dynamicendpoint_automation_assistant 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 Dynamicendpoint_automation_assistant. 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.
Dynamicendpoint_automation_assistant is provided by the Microsoft 365 Core MCP Server MCP server (roycedamien/m365-core-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 →