AI agents invoke report_generator to trigger actions in Panda Odoo MCP Server. 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.
Generating a report in Odoo executes server-side logic to compile, render, and produce a document (PDF, Excel, etc.). This goes beyond a simple read — it triggers an operation with side effects such as file creation and resource consumption. It does not modify or delete records, so Execute is the most appropriate category.
From the tool's definition "Generate an Odoo report" — triggers report generation, an external operation within Odoo that may invoke server-side rendering, data aggregation, and file creation
Documented attack patterns abuse exactly the kind of access report_generator gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Panda Odoo MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for report_generator:
{
"version": "1",
"default": "deny",
"tools": {
"report_generator": {
"limits": [
{
"counter": "report_generator_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} report_generator 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.
Free to start. No card required.
Generate an Odoo report. It is categorised as a Execute tool in the Panda Odoo MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Panda Odoo MCP Server MCP server in PolicyLayer and add a rule for report_generator: 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 Panda Odoo MCP Server. Nothing to install.
report_generator is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the report_generator 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 report_generator. 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.
report_generator is provided by the Panda Odoo MCP Server MCP server (pandeussilvae/mcp-odoo-panda). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Panda Odoo MCP Server, 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.
21 Panda Odoo MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.