tenant_restore
ADMIN: restore a tenant dump to a STAGING db by default
This record as markdown: /tools/rosenvladimirov-odoo-claude-mcp/tenant-restore.md
What tenant_restore does on Odoo Claude MCP
AI agents call tenant_restore 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 tenant_restore is rated Critical
Restoring a database dump overwrites existing data irreversibly, destroying current state.
From the tool's definition restore a tenant dump to a STAGING db
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs tenant_restore 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 tenant_restore, this is the rule to start with:
tenant_restore 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 tenant_restore call is checked against it from then on.
Questions about tenant_restore
ADMIN: restore a tenant dump to a STAGING db by default. 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 tenant_restore: 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.
tenant_restore 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 tenant_restore 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 tenant_restore. 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.
tenant_restore 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