Low Risk

odoo_refresh

Send a refresh notification to the user

How to control odoo_refresh ↓

What odoo_refresh does on Odoo Claude MCP

AI agents call odoo_refresh as a supporting operation in Odoo Claude MCP workflows.

Low Risk

Why odoo_refresh needs a policy

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:

How to control odoo_refresh

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:

policy.json
{
  "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.

  1. Create a free account and register Odoo Claude MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
SET A RULE FOR THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about odoo_refresh

What does the odoo_refresh tool do? +

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.

How do I enforce a policy on odoo_refresh? +

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.

What risk level is odoo_refresh? +

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

Can I rate-limit odoo_refresh? +

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.

How do I block odoo_refresh completely? +

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.

What MCP server provides odoo_refresh? +

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.

Enforce policy on every Odoo Claude MCP tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.