odoo_propose_view_patch · Odooclaw MCP: Risk & Policy

WHAT IT DOES

What odoo_propose_view_patch does on Odooclaw

AI agents use odoo_propose_view_patch to create or update resources in Odooclaw — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Odooclaw environment.

WHY IT NEEDS A POLICY

Why odoo_propose_view_patch needs a policy

The name suggests proposing/creating a view patch, which is a Write operation (creating/modifying data). However, the empty description significantly reduces confidence. Sibling tools like 'odoo_apply_view_patch_safe' suggest this tool may only propose (not apply) changes, keeping it in the Write category rather than Execute. Severity is medium given view changes could affect UI for all users.

From the tool's definition Tool name 'odoo_propose_view_patch' — 'propose' suggests creating or submitting a patch, 'view_patch' relates to UI view modifications. Description is empty.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

odoo_propose_view_patch Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "odoo_propose_view_patch": {
      "limits": [
        {
          "counter": "odoo_propose_view_patch_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Odooclaw, so you can run agents against it safely.

FAQ

Questions about odoo_propose_view_patch

What does the odoo_propose_view_patch tool do? +

odoo_propose_view_patch. It is categorised as a Write tool in the Odooclaw MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on odoo_propose_view_patch? +

Register the Odooclaw MCP server in PolicyLayer and add a rule for odoo_propose_view_patch: 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 Odooclaw. Nothing to install.

What risk level is odoo_propose_view_patch? +

odoo_propose_view_patch is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit odoo_propose_view_patch? +

Yes. Add a rate_limit block to the odoo_propose_view_patch 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 odoo_propose_view_patch completely? +

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

odoo_propose_view_patch is provided by the Odooclaw MCP server (nicolasramos/odooclaw-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.