AI agents call odoo_refresh as a supporting operation in Odoo Claude MCP workflows.
This tool sends a UI refresh notification to the user, which is a UI/signaling action rather than reading, writing, executing code, deleting data, or moving money. It has minimal blast radius as it only triggers a display refresh. Confidence is moderate because the description is brief and the exact mechanism is unclear.
From the tool's definition Send a refresh notification to the user
Documented attack patterns abuse exactly the kind of access odoo_refresh gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Odoo Claude MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for odoo_refresh:
{
"version": "1",
"default": "deny",
"tools": {
"odoo_refresh": {
"limits": [
{
"counter": "odoo_refresh_rate",
"window": "minute",
"max": 60,
"scope": "grant"
}
]
}
}
} odoo_refresh gets a rate cap, and everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Send a refresh notification to the user. It is categorised as a Other tool in the Odoo Claude MCP MCP Server, which means it performs auxiliary operations.
Register the Odoo Claude MCP server in PolicyLayer and add a rule for odoo_refresh: 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.
odoo_refresh is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the odoo_refresh 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 odoo_refresh. 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.
odoo_refresh 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.
Start from Odoo Claude MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
180 Odoo Claude MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.