client_onboard_status

ADMIN: read-only onboarding state for a slug/VAT

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/client-onboard-status.md

WHAT IT DOES

What client_onboard_status does on Odoo Claude MCP

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

Retrieves onboarding status without modification or side effects; admin read-only query only.

From the tool's definition read-only onboarding state for a slug/VAT

Risk signalsAdmin/system-level operation

Attacks that exploit this kind of access

RECOMMENDED RULE

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

client_onboard_status Allowed

client_onboard_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": {
    "client_onboard_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 client_onboard_status call is checked against it from then on.

FAQ

Questions about client_onboard_status

What does the client_onboard_status tool do? +

ADMIN: read-only onboarding state for a slug/VAT. 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 client_onboard_status? +

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

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

Can I rate-limit client_onboard_status? +

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

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

client_onboard_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 →