Critical Risk →

user_connection_delete

Delete a personal connection.

How to control user_connection_delete ↓

What user_connection_delete does on Odoo Claude MCP

AI agents call user_connection_delete 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 user_connection_delete needs a policy

This tool permanently removes a personal connection object from the system. Deletion is irreversible and cannot be undone programmatically. While the blast radius is scoped to a single connection record (not multiple records or cascading deletes), it is still a destructive operation. Classified as Destructive rather than Write because deletion cannot be reversed.

From the tool's definition 'Delete a personal connection' — the verb 'delete' and the irreversible nature of removing a connection record.

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

How to control user_connection_delete

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

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

user_connection_delete 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 user_connection_delete

What does the user_connection_delete tool do? +

Delete a personal connection. 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 user_connection_delete? +

Register the Odoo Claude MCP server in PolicyLayer and add a rule for user_connection_delete: 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 user_connection_delete? +

user_connection_delete 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 user_connection_delete? +

Yes. Add a rate_limit block to the user_connection_delete 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 user_connection_delete completely? +

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

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