email_flag · M365 MCP: Risk & Policy

WHAT IT DOES

What email_flag does on M365

AI agents use email_flag to create or update resources in M365 — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your M365 environment.

WHY IT NEEDS A POLICY

Why email_flag needs a policy

The tool name 'email_flag' indicates modification of email properties (flagging for follow-up, marking priority, etc.), which is a reversible Write operation. The empty description reduces confidence slightly, but the context (Outlook email management via M365-MCP) and naming pattern clearly suggest metadata mutation rather than data retrieval (Read) or destruction (Destructive).

From the tool's definition Tool named 'email_flag' on M365 Outlook management server; 'flag' action modifies email metadata/state without deletion.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

email_flag Rate-limited

email_flag 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": {
    "email_flag": {
      "limits": [
        {
          "counter": "email_flag_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 M365, so you can run agents against it safely.

FAQ

Questions about email_flag

What does the email_flag tool do? +

email_flag. It is categorised as a Write tool in the M365 MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on email_flag? +

Register the M365 MCP server in PolicyLayer and add a rule for email_flag: 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 M365. Nothing to install.

What risk level is email_flag? +

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

Can I rate-limit email_flag? +

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

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

email_flag is provided by the M365 MCP server (robin-collins/m365-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.