AI agents use create_calendar_event to create or update resources in Get Gather — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Get Gather environment.
Calendar event creation is a Write operation—it creates new data reversibly (events can be deleted or modified later). Severity is medium because misuse could spam calendars or create misleading schedule entries, but the blast radius is typically limited to one user's calendar.
From the tool's definition Tool name 'create_calendar_event' indicates creation of a calendar event, which modifies data in a calendar system. The description is empty, limiting specificity.
Documented attack patterns abuse exactly the kind of access create_calendar_event gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Get Gather, and nothing reaches the server without passing your rules. This is the rule we recommend for create_calendar_event:
{
"version": "1",
"default": "deny",
"tools": {
"create_calendar_event": {
"limits": [
{
"counter": "create_calendar_event_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_calendar_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.
Free to start. No card required.
create_calendar_event. It is categorised as a Write tool in the Get Gather MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Get Gather MCP server in PolicyLayer and add a rule for create_calendar_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 Get Gather. Nothing to install.
create_calendar_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_calendar_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_calendar_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_calendar_event is provided by the Get Gather MCP server (remotebrowser/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 62 Get Gather tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
62 Get Gather tools catalogued and risk-classified — across an index of 42,500+ MCP servers.