copy_event · Calendar MCP Server MCP: Risk & Policy

WHAT IT DOES

What copy_event does on Calendar MCP Server

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

WHY IT NEEDS A POLICY

Why copy_event needs a policy

The copy_event tool creates a new event record in a destination calendar, which is a reversible write operation. While it modifies calendar state by adding data, it does not delete or irreversibly alter existing events. The severity is medium because misuse could create duplicate or unwanted calendar entries affecting scheduling across multiple systems, but the action is reversible (the copied event can be deleted).

From the tool's definition Tool description states it will 'copy an event from one calendar/provider to another' and 'manually syncing individual events between different calendar systems', which involves creating/duplicating event data in a new location.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

copy_event Rate-limited

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

FAQ

Questions about copy_event

What does the copy_event tool do? +

Copy an event from one calendar/provider to another. Useful for manually syncing individual events between different calendar systems. It is categorised as a Write tool in the Calendar 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 copy_event? +

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

What risk level is copy_event? +

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

Can I rate-limit copy_event? +

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

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

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