manage_named_locations · Microsoft 365 Core MCP Server MCP

WHAT IT DOES

What manage_named_locations does on Microsoft 365 Core MCP Server

AI agents use manage_named_locations to create or update resources in Microsoft 365 Core MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Microsoft 365 Core MCP Server environment.

WHY IT NEEDS A POLICY

Why manage_named_locations needs a policy

This tool modifies security policy configurations (Conditional Access named locations) that directly impact authentication and access control decisions across Microsoft 365. While not irreversible (locations can be reconfigured), the changes are security-critical and affect who can access organizational resources. Misuse could lock out legitimate users or grant access to unauthorized parties.

From the tool's definition Manage Conditional Access named locations including IP address ranges and country/region locations for location-based access control. The verb 'manage' encompasses create, update, and modify operations on security policy configurations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

manage_named_locations Rate-limited

manage_named_locations stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "manage_named_locations": {
      "limits": [
        {
          "counter": "manage_named_locations_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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 manage_named_locations

What does the manage_named_locations tool do? +

Manage Conditional Access named locations including IP address ranges and country/region locations for location-based access control. It is categorised as a Write tool in the Microsoft 365 Core MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on manage_named_locations? +

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

manage_named_locations is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit manage_named_locations? +

Yes. Add a rate_limit block to the manage_named_locations 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 manage_named_locations completely? +

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

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