session_revoke
Revoke one MCP session (admin, or your own): marks the row
This record as markdown: /tools/rosenvladimirov-odoo-claude-mcp/session-revoke.md
What session_revoke does on Odoo Claude MCP
AI agents call session_revoke 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 session_revoke is rated Critical
Revoking a session permanently invalidates it, which cannot be undone (the session cannot be restored, only a new one created). This is irreversible by nature. With admin capability, an attacker could revoke other users' sessions, causing denial of service. Severity is high due to the admin-level blast radius affecting multiple users' access.
From the tool's definition 'Revoke one MCP session' — revoking a session is an irreversible invalidation action; 'marks the row' suggests a state change that terminates access
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs session_revoke 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 session_revoke, this is the rule to start with:
session_revoke 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 session_revoke call is checked against it from then on.
Questions about session_revoke
Revoke one MCP session (admin, or your own): marks the row. 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 session_revoke: 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.
session_revoke 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 session_revoke 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 session_revoke. 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.
session_revoke 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