AI agents use create_security_rules to create or update resources in Odoo Dev MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Odoo Dev MCP environment.
This tool appears to generate or create security rule definitions for Odoo modules. Security rules in Odoo control data access and permissions, making them configuration objects that can be created and modified. This falls into Write category (reversible creation/modification) rather than Execute or Destructive, as rule creation typically does not execute arbitrary code or permanently delete data.
From the tool's definition Tool name 'create_security_rules' indicates creation of security rules in Odoo; sibling tools consistently follow a 'create_' naming pattern for Write operations (create_odoo_model, create_odoo_module, create_odoo_view, etc.); empty description reduces…
Documented attack patterns abuse exactly the kind of access create_security_rules gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Odoo Dev MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for create_security_rules:
{
"version": "1",
"default": "deny",
"tools": {
"create_security_rules": {
"limits": [
{
"counter": "create_security_rules_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_security_rules 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.
Free to start. No card required.
create_security_rules. It is categorised as a Write tool in the Odoo Dev MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Odoo Dev MCP server in PolicyLayer and add a rule for create_security_rules: 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 Dev MCP. Nothing to install.
create_security_rules is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_security_rules 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 create_security_rules. 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.
create_security_rules is provided by the Odoo Dev MCP server (mart337i/odoo-dev-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Odoo Dev 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.
25 Odoo Dev MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.