AI agents use google_calendar_create_event to create or update resources in Odoo Claude MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Odoo Claude MCP environment.
This tool creates calendar events, which is a Write action—it generates new data that persists in the calendar system. Severity is medium because misconfigured events could disrupt scheduling, add unwanted invitations, or spam calendar participants, but the action is reversible (events can be deleted).
From the tool's definition Tool name 'google_calendar_create_event' and description 'Create a new calendar event' indicate creation of new data in Google Calendar.
Documented attack patterns abuse exactly the kind of access google_calendar_create_event gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Odoo Claude MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for google_calendar_create_event:
{
"version": "1",
"default": "deny",
"tools": {
"google_calendar_create_event": {
"limits": [
{
"counter": "google_calendar_create_event_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} google_calendar_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 Odoo Claude MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Odoo Claude MCP server in PolicyLayer and add a rule for google_calendar_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 Odoo Claude MCP. Nothing to install.
google_calendar_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 google_calendar_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 google_calendar_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.
google_calendar_create_event is provided by the Odoo Claude MCP server (rosenvladimirov/odoo-claude-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Odoo Claude MCP, 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.
180 Odoo Claude MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.