AI agents use create_event to create or update resources in Google Toolbox — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Google Toolbox environment.
This tool creates new calendar events, which is a Write operation that modifies calendar data. While reversible (events can be deleted), it could be misused by an AI agent to spam calendar invitations, create misleading meetings, or schedule fraudulent events.
From the tool's definition Tool description states 'Create a new calendar event' - a reversible creation of new data in Google Calendar.
Documented attack patterns abuse exactly the kind of access create_event gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Google Toolbox, and nothing reaches the server without passing your rules. This is the rule we recommend for create_event:
{
"version": "1",
"default": "deny",
"tools": {
"create_event": {
"limits": [
{
"counter": "create_event_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}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.
Free to start. No card required.
Create a new calendar event. It is categorised as a Write tool in the Google Toolbox MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Google Toolbox 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 Google Toolbox. 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 Google Toolbox MCP server (jikime/py-mcp-google-toolbox). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Google Toolbox, 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.
11 Google Toolbox tools catalogued and risk-classified — across an index of 43,000+ MCP servers.