Raw HTTP request to any Odoo controller URL via web session.
AI agents invoke odoo_web_request 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.
This tool can send arbitrary HTTP requests to any Odoo controller endpoint using an authenticated web session. The scope is unlimited — it can trigger reads, writes, deletions, financial transactions, or any other action exposed by Odoo's controllers. Because it encompasses all possible operations (including Financial and Destructive), it must be classified at the most severe applicable category.
From the tool's definition Raw HTTP request to any Odoo controller URL via web session
Documented attack patterns abuse exactly the kind of access odoo_web_request gives an agent:
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_web_request:
{
"version": "1",
"default": "deny",
"tools": {
"odoo_web_request": {
"limits": [
{
"counter": "odoo_web_request_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} odoo_web_request 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.
Raw HTTP request to any Odoo controller URL via web session. 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.
Register the Odoo Claude MCP server in PolicyLayer and add a rule for odoo_web_request: 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.
odoo_web_request 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 odoo_web_request 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 odoo_web_request. 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.
odoo_web_request 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.
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.