Low Risk

oca_status

Show git status of all OCA repos (branch, clean, behind, modules count).

How to control oca_status ↓

What oca_status does on Odoo Claude MCP

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

Low Risk

Why oca_status needs a policy

The tool only reads and reports git repository metadata. It performs no write, execution, deletion, or financial operations. The 'show' verb and the nature of git status as a read-only inspection command confirm this is purely informational retrieval with no side effects.

From the tool's definition Tool description states 'Show git status' — a display/query operation that retrieves repository state (branch, clean status, behind commits, modules count) without modifying any data.

Documented attack patterns abuse exactly the kind of access oca_status gives an agent:

How to control oca_status

PolicyLayer is an MCP gateway — it sits between your AI agents and Odoo Claude MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for oca_status:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "oca_status": {}
  }
}

oca_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Odoo Claude MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about oca_status

What does the oca_status tool do? +

Show git status of all OCA repos (branch, clean, behind, modules count). 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 oca_status? +

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

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

Can I rate-limit oca_status? +

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

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

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

Enforce policy on every Odoo Claude MCP tool call.

Start from Odoo Claude MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

180 Odoo Claude MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.