call_microsoft_api · Microsoft 365 Core MCP Server MCP

WHAT IT DOES

What call_microsoft_api does on Microsoft 365 Core MCP Server

AI agents invoke call_microsoft_api 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.

WHY IT NEEDS A POLICY

Why call_microsoft_api needs a policy

This tool provides unrestricted access to the entire Microsoft Graph and Azure Resource Management API surface with full HTTP method control (GET, POST, PUT, PATCH, DELETE, etc.). An AI agent could use it to perform any operation across Microsoft 365 services including Teams, SharePoint, Exchange, Intune, Azure AD, and Azure resources.

From the tool's definition 'Make direct calls to any Microsoft Graph or Azure Resource Management API endpoint with full control over HTTP methods and parameters'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

call_microsoft_api Rate-limited

call_microsoft_api stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "call_microsoft_api": {
      "limits": [
        {
          "counter": "call_microsoft_api_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Microsoft 365 Core MCP Server, so you can run agents against it safely.

FAQ

Questions about call_microsoft_api

What does the call_microsoft_api tool do? +

Make direct calls to any Microsoft Graph or Azure Resource Management API endpoint with full control over HTTP methods and parameters. 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.

How do I enforce a policy on call_microsoft_api? +

Register the Microsoft 365 Core MCP Server MCP server in PolicyLayer and add a rule for call_microsoft_api: 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.

What risk level is call_microsoft_api? +

call_microsoft_api is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit call_microsoft_api? +

Yes. Add a rate_limit block to the call_microsoft_api 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.

How do I block call_microsoft_api completely? +

Set action: deny in the PolicyLayer policy for call_microsoft_api. 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.

What MCP server provides call_microsoft_api? +

call_microsoft_api 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.