manage_sensitivity_labels

WHAT IT DOES

What manage_sensitivity_labels does on Microsoft 365 Core MCP Server

AI agents use manage_sensitivity_labels 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_sensitivity_labels needs a policy

Sensitivity labels are reversible configurations that classify and protect data but do not delete or permanently modify underlying content. This aligns with Write category (create/modify). Severity is high because misuse could broadly reclassify sensitive organizational data, alter compliance posture, or expose/restrict access to resources unexpectedly.

From the tool's definition Tool name 'manage_sensitivity_labels' with empty description. In Microsoft 365 context, sensitivity labels control data classification and protection across documents, emails, and content.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

manage_sensitivity_labels Rate-limited

manage_sensitivity_labels 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_sensitivity_labels": {
      "limits": [
        {
          "counter": "manage_sensitivity_labels_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_sensitivity_labels

What does the manage_sensitivity_labels tool do? +

manage_sensitivity_labels. 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_sensitivity_labels? +

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

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

Can I rate-limit manage_sensitivity_labels? +

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

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

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