odoo_close_activity_with_reason

WHAT IT DOES

What odoo_close_activity_with_reason does on Odooclaw

AI agents use odoo_close_activity_with_reason 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_close_activity_with_reason needs a policy

Closing an activity in an ERP system is a reversible write operation—the activity state changes but the action can theoretically be undone or reopened. This is not destructive (data remains) and not execute-level (no arbitrary code/commands).

From the tool's definition Tool name 'odoo_close_activity_with_reason' indicates a state-change operation on an activity record. The 'close' action modifies data (marks activity as closed) and the 'with_reason' parameter suggests capturing justification for an audit trail.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

odoo_close_activity_with_reason Rate-limited

odoo_close_activity_with_reason 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_close_activity_with_reason": {
      "limits": [
        {
          "counter": "odoo_close_activity_with_reason_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_close_activity_with_reason

What does the odoo_close_activity_with_reason tool do? +

odoo_close_activity_with_reason. 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_close_activity_with_reason? +

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

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

Can I rate-limit odoo_close_activity_with_reason? +

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

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

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