create_event
Create a new calendar event. Recurring events cannot be created via automation. Attendees cannot be added programmatically.
This record as markdown: /tools/heznpc-airmcp/create-event.md
What create_event does on AirMCP
AI agents use create_event to create or update resources in AirMCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AirMCP environment.
Why create_event is rated Medium
This tool creates calendar entries, which is a reversible write operation. The severity is medium rather than high because: (1) calendar events can be deleted or modified to undo mistakes, (2) the tool has intentional limitations (no recurring events, no programmatic attendee addition) that reduce potential for harmful automation, and (3) the blast radius of accidental misuse is limited to calendar clutter rather…
From the tool's definition Tool name is 'create_event' and description states 'Create a new calendar event.' This is an explicit create operation that adds new data to the user's calendar system.
Attacks that exploit this kind of access
The rule that runs create_event safely
PolicyLayer is an MCP gateway: it sits between your AI agents and AirMCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_event, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect AirMCP, apply this rule, and every create_event call is checked against it from then on.
Questions about create_event
Create a new calendar event. Recurring events cannot be created via automation. Attendees cannot be added programmatically. It is categorised as a Write tool in the AirMCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Air MCP server in PolicyLayer and add a rule for 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 AirMCP. Nothing to install.
create_event 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_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.
Set action: deny in the PolicyLayer policy for 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.
create_event is provided by the Air MCP server (airmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Air, and thousands of servers like it.
This server
Across the catalogue