who_am_i

Show current user identity and active connection.

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/who-am-i.md

WHAT IT DOES

What who_am_i does on Odoo Claude MCP

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

This tool retrieves information about the current authenticated user and connection state. It is a read-only operation that does not modify, delete, execute, or commit financial transactions. The blast radius of misuse is minimal—an agent could learn the identity of the user account it is running under, which is informational rather than harmful. No state changes occur.

From the tool's definition Tool name 'who_am_i' and description 'Show current user identity and active connection' indicate a query/retrieval operation with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

who_am_i Allowed

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

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

FAQ

Questions about who_am_i

What does the who_am_i tool do? +

Show current user identity and active connection. 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 who_am_i? +

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

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

Can I rate-limit who_am_i? +

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

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

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