calendar_update · Mailgent MCP Server MCP: Risk & Policy

WHAT IT DOES

What calendar_update does on Mailgent MCP Server

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

WHY IT NEEDS A POLICY

Why calendar_update needs a policy

This tool creates or modifies data reversibly by updating calendar events. It is not destructive (does not delete), not financial, and not execute (does not run arbitrary code). The severity is medium because unauthorized calendar updates could disrupt scheduling and communications, but changes are typically reversible and the blast radius is limited to calendar integrity.

From the tool's definition Tool name 'calendar_update' and description 'Update an existing calendar event' indicate modification of existing data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

calendar_update Rate-limited

calendar_update 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": {
    "calendar_update": {
      "limits": [
        {
          "counter": "calendar_update_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 Mailgent MCP Server, so you can run agents against it safely.

FAQ

Questions about calendar_update

What does the calendar_update tool do? +

Update an existing calendar event. It is categorised as a Write tool in the Mailgent 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 calendar_update? +

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

What risk level is calendar_update? +

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

Can I rate-limit calendar_update? +

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

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

calendar_update is provided by the Mailgent MCP Server MCP server (loomal-ai/loomal-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.