tenant_current

Return the currently active tenant (or null) and its tool count.

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/tenant-current.md

WHAT IT DOES

What tenant_current does on Odoo Claude MCP

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

Retrieves tenant metadata without modifying state or exposing sensitive operational data.

From the tool's definition Return the currently active tenant and its tool count.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

tenant_current Allowed

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

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

FAQ

Questions about tenant_current

What does the tenant_current tool do? +

Return the currently active tenant (or null) and its tool 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 tenant_current? +

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

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

Can I rate-limit tenant_current? +

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

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

tenant_current 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

The MCP Attack Database →

Guides

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