force_sync · Email MCP: Risk & Policy

WHAT IT DOES

What force_sync does on Email

AI agents invoke force_sync to trigger actions in Email. 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 force_sync needs a policy

This tool executes an external operation by triggering Outlook's Send/Receive mechanism via COM automation. It is not a pure read (it initiates network sync operations), not destructive, not financial, and not a simple write. It falls squarely in Execute as it runs an external process/operation whose effects depend on the current state of configured sync groups.

From the tool's definition 'Trigger Outlook Send/Receive and block until all configured sync groups finish' — actively triggers an external operation (Outlook COM automation sync) and blocks until completion

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

force_sync Rate-limited

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

FAQ

Questions about force_sync

What does the force_sync tool do? +

Trigger Outlook Send/Receive and block until all configured sync groups finish (or timeout). Useful before querying to make sure recent server-side mail is local. Returns per-group elapsed time and a timed_out flag. It is categorised as a Execute tool in the Email MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on force_sync? +

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

What risk level is force_sync? +

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

Can I rate-limit force_sync? +

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

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

force_sync is provided by the Email MCP server (kerodkibatu/email-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.