module_deploy_history

ADMIN: list past deploy/rollback ops (optionally per target).

SERVEROdoo Claude MCP SOURCErosenvladimirov/odoo-claude-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/rosenvladimirov-odoo-claude-mcp/module-deploy-history.md

WHAT IT DOES

What module_deploy_history does on Odoo Claude MCP

AI agents call module_deploy_history to retrieve information from Odoo Claude MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why module_deploy_history is rated Low

Tool only retrieves historical deployment records; no side effects.

From the tool's definition list past deploy/rollback ops

Risk signalsAdmin/system-level operation

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs module_deploy_history 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 module_deploy_history, this is the rule to start with:

module_deploy_history Allowed

module_deploy_history is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "module_deploy_history": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Odoo Claude MCP, apply this rule, and every module_deploy_history call is checked against it from then on.

FAQ

Questions about module_deploy_history

What does the module_deploy_history tool do? +

ADMIN: list past deploy/rollback ops (optionally per target). It is categorised as a Read tool in the Odoo Claude MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on module_deploy_history? +

Register the Odoo Claude MCP server in PolicyLayer and add a rule for module_deploy_history: 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.

What risk level is module_deploy_history? +

module_deploy_history is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit module_deploy_history? +

Yes. Add a rate_limit block to the module_deploy_history 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.

How do I block module_deploy_history completely? +

Set action: deny in the PolicyLayer policy for module_deploy_history. 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.

What MCP server provides module_deploy_history? +

module_deploy_history 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.

KEEP EXPLORING

More on Odoo Claude, and thousands of servers like it.

This server

All 246 Odoo Claude tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →