Critical Risk →

google_calendar_delete_event

Delete a calendar event.

How to control google_calendar_delete_event ↓

What google_calendar_delete_event does on Odoo Claude MCP

AI agents call google_calendar_delete_event to permanently remove resources in Odoo Claude MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why google_calendar_delete_event needs a policy

Deleting a calendar event is an irreversible action that cannot be undone through normal means. Once deleted, the event and associated metadata are removed from the calendar system. This fits the Destructive category as it permanently removes data.

From the tool's definition Tool name is 'google_calendar_delete_event' and description states 'Delete a calendar event.' The verb 'delete' combined with calendar event removal indicates irreversible data destruction.

Documented attack patterns abuse exactly the kind of access google_calendar_delete_event gives an agent:

How to control google_calendar_delete_event

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_delete_event:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "google_calendar_delete_event"
  ]
}

google_calendar_delete_event disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register Odoo Claude MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about google_calendar_delete_event

What does the google_calendar_delete_event tool do? +

Delete a calendar event. It is categorised as a Destructive tool in the Odoo Claude MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on google_calendar_delete_event? +

Register the Odoo Claude MCP server in PolicyLayer and add a rule for google_calendar_delete_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.

What risk level is google_calendar_delete_event? +

google_calendar_delete_event is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit google_calendar_delete_event? +

Yes. Add a rate_limit block to the google_calendar_delete_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.

How do I block google_calendar_delete_event completely? +

Set action: deny in the PolicyLayer policy for google_calendar_delete_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.

What MCP server provides google_calendar_delete_event? +

google_calendar_delete_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.

Enforce policy on every Odoo Claude MCP tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.