execute_report · Odoo- MCP: Risk & Policy

WHAT IT DOES

What execute_report does on Odoo-MCP

AI agents invoke execute_report to trigger actions in Odoo-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.

WHY IT NEEDS A POLICY

Why execute_report needs a policy

This tool executes reports in an Odoo ERP system. While report generation is not inherently destructive or financial, 'execute' indicates triggering computational or process-driven operations whose side effects depend on report configuration and arguments. Reports in ERP systems often trigger workflows, generate files, queue jobs, or update intermediate data.

From the tool's definition Tool name is 'execute_report' with description 'Execute reports and get results'. The verb 'execute' indicates runtime action. In Odoo ERP context, reports can trigger complex business logic, generate data exports, or interact with external systems.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

execute_report Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "execute_report": {
      "limits": [
        {
          "counter": "execute_report_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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 execute_report

What does the execute_report tool do? +

Execute reports and get results. It is categorised as a Execute tool in the Odoo-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 execute_report? +

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

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

Can I rate-limit execute_report? +

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

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

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