AI agents use create-batch-events to create or update resources in macOS Calendar MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your macOS Calendar MCP Server environment.
The tool creates calendar entries in bulk, which is a Write-category action (creates/modifies data reversibly). Severity is medium because bulk event creation could clutter calendars or interfere with scheduling if misused by an agent, but the effects are not destructive or irreversible—events can be manually deleted.
From the tool's definition Tool name 'create-batch-events' and description '批量创建事件' (batch create events) indicate this creates multiple calendar events. This is a reversible write operation that modifies calendar data without deletion.
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access create-batch-events gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and macOS Calendar MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for create-batch-events:
{
"version": "1",
"default": "deny",
"tools": {
"create-batch-events": {
"limits": [
{
"counter": "create-batch-events_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create-batch-events 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.
Free to start. No card required.
批量创建事件. It is categorised as a Write tool in the macOS Calendar MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the macOS Calendar MCP Server MCP server in PolicyLayer and add a rule for create-batch-events: 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 macOS Calendar MCP Server. Nothing to install.
create-batch-events is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create-batch-events 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.
Set action: deny in the PolicyLayer policy for create-batch-events. 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.
create-batch-events is provided by the macOS Calendar MCP Server MCP server (xybstone/macos-calendar-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from macOS Calendar MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
8 macOS Calendar MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.