create_calendar_event · TrekMail MCP Server MCP

WHAT IT DOES

What create_calendar_event does on TrekMail MCP Server

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

WHY IT NEEDS A POLICY

Why create_calendar_event needs a policy

Creating a calendar event is a write operation that adds new data to the system. It is reversible (the event can be deleted or modified), so it does not qualify as Destructive. It does not execute arbitrary code, trigger external operations with argument-dependent effects, or move money, so Execute and Financial are not applicable.

From the tool's definition Tool name 'create_calendar_event' and description 'Create a new calendar event' indicate data creation/modification. This is a reversible write operation that adds a new record to a calendar system.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_calendar_event Rate-limited

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

FAQ

Questions about create_calendar_event

What does the create_calendar_event tool do? +

Create a new calendar event. It is categorised as a Write tool in the TrekMail 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 create_calendar_event? +

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

What risk level is create_calendar_event? +

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

Can I rate-limit create_calendar_event? +

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

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

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