fleet_upgrade
ADMIN: canary-upgrade ONE stack to a target image tag.
This record as markdown: /tools/rosenvladimirov-odoo-claude-mcp/fleet-upgrade.md
What fleet_upgrade does on Odoo Claude MCP
AI agents invoke fleet_upgrade to trigger actions in Odoo Claude MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why fleet_upgrade is rated High
Triggers an upgrade operation on a running stack, with significant operational impact.
From the tool's definition canary-upgrade ONE stack to a target image tag
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs fleet_upgrade 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 fleet_upgrade, this is the rule to start with:
fleet_upgrade stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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 fleet_upgrade call is checked against it from then on.
Questions about fleet_upgrade
ADMIN: canary-upgrade ONE stack to a target image tag. It is categorised as a Execute tool in the Odoo Claude MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Odoo Claude MCP server in PolicyLayer and add a rule for fleet_upgrade: 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.
fleet_upgrade is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the fleet_upgrade 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 fleet_upgrade. 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.
fleet_upgrade 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