identify_totp_disable
Disable TOTP two-factor for YOUR current identified profile (removes the stored secret).
This record as markdown: /tools/rosenvladimirov-odoo-claude-mcp/identify-totp-disable.md
What identify_totp_disable does on Odoo Claude MCP
AI agents use identify_totp_disable to create or update resources in Odoo Claude MCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Odoo Claude MCP environment.
Why identify_totp_disable is rated Medium
Irreversibly disables 2FA security for current user account, reducing authentication security posture significantly.
From the tool's definition Disable TOTP two-factor, removes the stored secret
Attacks that exploit this kind of access
The rule that runs identify_totp_disable 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 identify_totp_disable, this is the rule to start with:
identify_totp_disable stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Odoo Claude MCP, apply this rule, and every identify_totp_disable call is checked against it from then on.
Questions about identify_totp_disable
Disable TOTP two-factor for YOUR current identified profile (removes the stored secret). It is categorised as a Write tool in the Odoo Claude MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Odoo Claude MCP server in PolicyLayer and add a rule for identify_totp_disable: 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.
identify_totp_disable is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the identify_totp_disable 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 identify_totp_disable. 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.
identify_totp_disable 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.
This server
Across the catalogue