manage_settings · Odoo- MCP: Risk & Policy

WHAT IT DOES

What manage_settings does on Odoo-MCP

AI agents use manage_settings to create or update resources in Odoo-MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Odoo-MCP environment.

WHY IT NEEDS A POLICY

Why manage_settings needs a policy

Configuration changes in ERP systems are reversible modifications that can affect system behavior, access controls, or business logic. However, since the description is generic and doesn't specify exact scope (system-wide vs. module-specific settings), severity is high rather than critical. The tool could impact many users if misconfigured, but changes are typically reversible through re-configuration or rollback.

From the tool's definition Tool name 'manage_settings' with description 'Configuration and settings management' indicates modification of system configuration. In Odoo ERP context, settings management typically creates or modifies configuration records reversibly.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

manage_settings Rate-limited

manage_settings stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "manage_settings": {
      "limits": [
        {
          "counter": "manage_settings_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Odoo-MCP, so you can run agents against it safely.

FAQ

Questions about manage_settings

What does the manage_settings tool do? +

Configuration and settings management. It is categorised as a Write tool in the Odoo-MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on manage_settings? +

Register the Odoo- MCP server in PolicyLayer and add a rule for manage_settings: 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-MCP. Nothing to install.

What risk level is manage_settings? +

manage_settings is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit manage_settings? +

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

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

manage_settings is provided by the Odoo- MCP server (ridrisa/odoo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.