ee_license_status

Read Enterprise license status from an Odoo instance (expiration, code, reason).

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/ee-license-status.md

WHAT IT DOES

What ee_license_status does on Odoo Claude MCP

AI agents call ee_license_status 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 ee_license_status is rated Low

This tool queries and retrieves license metadata from an Odoo instance without creating, modifying, or deleting data. It is a passive information-gathering operation with minimal blast radius if misused by an AI agent—at worst, an agent learns about license status, which is non-sensitive operational metadata.

From the tool's definition Tool name and description explicitly state 'Read Enterprise license status' and retrieves data (expiration, code, reason) with no modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

ee_license_status Allowed

ee_license_status 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": {
    "ee_license_status": {}
  }
}

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 ee_license_status call is checked against it from then on.

FAQ

Questions about ee_license_status

What does the ee_license_status tool do? +

Read Enterprise license status from an Odoo instance (expiration, code, reason). 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 ee_license_status? +

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

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

Can I rate-limit ee_license_status? +

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

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

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

KEEP EXPLORING

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

This server

All 246 Odoo Claude tools →

Across the catalogue

editor_status on 010 Editor → The MCP Attack Database →

Guides

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