High Risk →

open_connection_manager

Open the Connection Manager GUI (desktop app).

How to control open_connection_manager ↓

What open_connection_manager does on Odoo Claude MCP

AI agents invoke open_connection_manager to trigger actions in Odoo Claude MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

High Risk

Why open_connection_manager needs a policy

This tool triggers an external operation — opening a GUI application on the desktop. It doesn't just read or write data; it launches/executes a desktop application process. The blast radius is medium because opening a connection manager could expose connection credentials or allow unauthorized connections to be configured, but it doesn't directly destroy data or move money.

From the tool's definition Open the Connection Manager GUI (desktop app)

Documented attack patterns abuse exactly the kind of access open_connection_manager gives an agent:

How to control open_connection_manager

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 open_connection_manager:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "open_connection_manager": {
      "limits": [
        {
          "counter": "open_connection_manager_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

open_connection_manager stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. 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.
RATE-LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about open_connection_manager

What does the open_connection_manager tool do? +

Open the Connection Manager GUI (desktop app). It is categorised as a Execute tool in the Odoo Claude MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on open_connection_manager? +

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

open_connection_manager is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit open_connection_manager? +

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

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

open_connection_manager 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.