manage_dlp_incidents · Microsoft 365 Core MCP Server MCP

WHAT IT DOES

What manage_dlp_incidents does on Microsoft 365 Core MCP Server

AI agents use manage_dlp_incidents 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_dlp_incidents needs a policy

This tool actively manages DLP (Data Loss Prevention) incidents by performing remediation actions and sending user notifications, which constitutes modifying system state (incident status, user alerts). While it also reads/investigates incidents, the dominant action is Write-level modification of incident records and triggering notifications.

From the tool's definition 'manage DLP incidents', 'user notifications and remediation actions' — implies modifying incident state, sending notifications, and taking remediation steps

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

manage_dlp_incidents Rate-limited

manage_dlp_incidents 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_dlp_incidents": {
      "limits": [
        {
          "counter": "manage_dlp_incidents_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_dlp_incidents

What does the manage_dlp_incidents tool do? +

Investigate and manage DLP policy violations and incidents including user notifications and remediation actions. 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_dlp_incidents? +

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

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

Can I rate-limit manage_dlp_incidents? +

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

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

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