ical__create_event · Mcp Ical Swift MCP: Risk & Policy

WHAT IT DOES

What ical__create_event does on Mcp Ical Swift

AI agents use ical__create_event to create or update resources in Mcp Ical Swift — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Ical Swift environment.

WHY IT NEEDS A POLICY

Why ical__create_event needs a policy

This tool creates new calendar events, which is a reversible write operation. It modifies calendar state by adding data but does not delete, execute code, or move money. The 'medium' severity reflects that malicious calendar event injection could spam a user, impersonate communications, or trigger unwanted notifications, but the impact is generally contained and reversible.

From the tool's definition Tool name 'ical__create_event' and description states 'Create a new calendar event in EventKit; visible in Apple Calendar.app and synced via iCloud'. The verb 'Create' and action of adding a new event to a calendar system indicates data creation/modification.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

ical__create_event Rate-limited

ical__create_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": {
    "ical__create_event": {
      "limits": [
        {
          "counter": "ical__create_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 Mcp Ical Swift, so you can run agents against it safely.

FAQ

Questions about ical__create_event

What does the ical__create_event tool do? +

Create a new calendar event in EventKit; visible in Apple Calendar.app and synced via iCloud if the chosen calendar is iCloud-backed. Returns. It is categorised as a Write tool in the Mcp Ical Swift MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on ical__create_event? +

Register the Mcp Ical Swift MCP server in PolicyLayer and add a rule for ical__create_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 Mcp Ical Swift. Nothing to install.

What risk level is ical__create_event? +

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

Can I rate-limit ical__create_event? +

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

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

ical__create_event is provided by the Mcp Ical Swift MCP server (sealjay/mcp-ical-swift). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.