Critical Risk →

odoo_web_logout

Destroy web session and logout.

How to control odoo_web_logout ↓

What odoo_web_logout does on Odoo Claude MCP

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

The tool irreversibly destroys the current web session and logs out the user. Session destruction is not easily reversible — the session data is gone and the user must re-authenticate. This is not a simple write/update but a destructive action on session state. Misuse by an AI agent could interrupt workflows and lock out active operations, warranting medium severity.

From the tool's definition Destroy web session and logout

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

How to control odoo_web_logout

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

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

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

What does the odoo_web_logout tool do? +

Destroy web session and logout. 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 odoo_web_logout? +

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

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

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

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

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