Create a calendar event. Does NOT send invites by default.
AI agents use calendar_create to create or update resources in Mariana Google MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mariana Google MCP environment.
This tool creates new calendar events, which is a reversible write operation. While calendar entries can be modified or deleted, the tool itself performs creation/addition of data without permanent destruction.
From the tool's definition Tool description states 'Create a calendar event' which is a write operation that creates new data. The clarification 'Does NOT send invites by default' indicates the tool creates reversible calendar entries without triggering external notifications by…
Attacks that exploit this kind of access
Create a calendar event. Does NOT send invites by default. It is categorised as a Write tool in the Mariana Google MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mariana Google MCP server in PolicyLayer and add a rule for calendar_create: 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 Mariana Google MCP. Nothing to install.
calendar_create 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 calendar_create 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 calendar_create. 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.
calendar_create is provided by the Mariana Google MCP server (marianasmall/mariana-google-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →