rename_calendar · Apple Calendar MCP Server MCP

WHAT IT DOES

What rename_calendar does on Apple Calendar MCP Server

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

WHY IT NEEDS A POLICY

Why rename_calendar needs a policy

Renaming a calendar is a non-destructive modification—the action can be undone by renaming again. It does not delete data (which would be Destructive), execute code (Execute), move money (Financial), or merely read data (Read).

From the tool's definition Tool name 'rename_calendar' and description 'Rename a calendar' indicate modification of calendar metadata. This is a reversible write operation that changes an existing calendar's name but does not delete data or execute arbitrary code.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

rename_calendar Rate-limited

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

FAQ

Questions about rename_calendar

What does the rename_calendar tool do? +

Rename a calendar. It is categorised as a Write tool in the Apple 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 rename_calendar? +

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

What risk level is rename_calendar? +

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

Can I rate-limit rename_calendar? +

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

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

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