odoo_mark_activity_done · Odooclaw MCP: Risk & Policy

WHAT IT DOES

What odoo_mark_activity_done does on Odooclaw

AI agents use odoo_mark_activity_done 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_mark_activity_done needs a policy

This tool performs a reversible state modification (marking an activity as complete) rather than deletion or execution of arbitrary logic. It fits the Write category as it updates an activity record. Severity is medium because misuse could mark important business activities as done incorrectly, affecting workflow tracking, but the operation is reversible via updating the activity status again.

From the tool's definition Tool name 'odoo_mark_activity_done' indicates a state-change operation on an activity record in Odoo ERP. The 'mark' verb suggests updating an activity's status to 'done', which modifies data reversibly. Description is empty, limiting evidence strength.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

odoo_mark_activity_done Rate-limited

odoo_mark_activity_done 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_mark_activity_done": {
      "limits": [
        {
          "counter": "odoo_mark_activity_done_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_mark_activity_done

What does the odoo_mark_activity_done tool do? +

odoo_mark_activity_done. 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_mark_activity_done? +

Register the Odooclaw MCP server in PolicyLayer and add a rule for odoo_mark_activity_done: 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_mark_activity_done? +

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

Can I rate-limit odoo_mark_activity_done? +

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

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

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