session_handoff_accept

Accept a handoff addressed to you. Materializes the

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/session-handoff-accept.md

WHAT IT DOES

What session_handoff_accept does on Odoo Claude MCP

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

Even though session_handoff_accept only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

session_handoff_accept Allowed

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

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

FAQ

Questions about session_handoff_accept

What does the session_handoff_accept tool do? +

Accept a handoff addressed to you. Materializes the. 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 session_handoff_accept? +

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

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

Can I rate-limit session_handoff_accept? +

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

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

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