odoo_web_logout
Destroy web session and logout.
This record as markdown: /tools/rosenvladimirov-odoo-claude-mcp/odoo-web-logout.md
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.
Why odoo_web_logout is rated Critical
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
Attacks that exploit this kind of access
The rule that runs odoo_web_logout safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Odoo Claude MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For odoo_web_logout, this is the rule to start with:
odoo_web_logout is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Odoo Claude MCP, apply this rule, and every odoo_web_logout call is checked against it from then on.
Questions about odoo_web_logout
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.
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.
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.
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.
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.
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.
More on Odoo Claude, and thousands of servers like it.
Across the catalogue