Low Risk

get_development_guidelines

get_development_guidelines

How to control get_development_guidelines ↓

What get_development_guidelines does on Odoo Dev MCP

AI agents call get_development_guidelines to retrieve information from Odoo Dev MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_development_guidelines needs a policy

This tool retrieves guidelines or documentation—a read operation with no side effects. Even though the description is empty, the name and context (an MCP server for Odoo development providing documentation) strongly suggest it fetches or queries stored guidelines rather than modifying state or executing code.

From the tool's definition Tool name 'get_development_guidelines' indicates retrieval of documentation or reference material. Description is empty, but the naming pattern aligns with the server's stated purpose of providing 'version-aware documentation links' and supporting development…

Documented attack patterns abuse exactly the kind of access get_development_guidelines gives an agent:

How to control get_development_guidelines

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 get_development_guidelines:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_development_guidelines": {}
  }
}

get_development_guidelines is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Odoo Dev MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_development_guidelines

What does the get_development_guidelines tool do? +

get_development_guidelines. It is categorised as a Read tool in the Odoo Dev MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_development_guidelines? +

Register the Odoo Dev MCP server in PolicyLayer and add a rule for get_development_guidelines: 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.

What risk level is get_development_guidelines? +

get_development_guidelines is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_development_guidelines? +

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

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

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

Enforce policy on every Odoo Dev MCP tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.