public_access_portal_home
Get portal home page content via web session (/my/home).
This record as markdown: /tools/rosenvladimirov-odoo-claude-mcp/public-access-portal-home.md
What public_access_portal_home does on Odoo Claude MCP
AI agents call public_access_portal_home 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.
Why public_access_portal_home is rated Low
This tool performs a read-only operation—fetching the home page content that a user would normally see through their portal session. There are no side effects, no data is created or modified, and no external operations are triggered. The endpoint itself (/my/home) is a standard portal view endpoint.
From the tool's definition Tool retrieves portal home page content via web session endpoint (/my/home). The verb 'Get' and the mechanism of retrieving existing page content indicate data retrieval with no modification, creation, deletion, or execution of operations.
Attacks that exploit this kind of access
The rule that runs public_access_portal_home 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 public_access_portal_home, this is the rule to start with:
public_access_portal_home is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Odoo Claude MCP, apply this rule, and every public_access_portal_home call is checked against it from then on.
Questions about public_access_portal_home
Get portal home page content via web session (/my/home). It is categorised as a Read tool in the Odoo Claude MCP MCP Server, which means it retrieves data without modifying state.
Register the Odoo Claude MCP server in PolicyLayer and add a rule for public_access_portal_home: 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.
public_access_portal_home is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the public_access_portal_home 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.
Set action: deny in the PolicyLayer policy for public_access_portal_home. 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.
public_access_portal_home 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.
More on Odoo Claude, and thousands of servers like it.
This server
Across the catalogue