search_documentation

THE RISK

Low Risk

Why search_documentation needs a policy

This tool searches for documentation—a read-only operation with no data modification, code execution, or side effects. The absence of a description lowers confidence slightly, but the name and server purpose (development workflows) strongly indicate documentation retrieval rather than state-changing actions.

From the tool's definition Tool name 'search_documentation' indicates a retrieval operation. The server description mentions 'provides version-aware documentation links', and this tool appears designed to search/retrieve that documentation.

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

POLICY

How to control search_documentation

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

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "search_documentation": {}
  }
}

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

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

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Odoo Dev MCP tools

Write create_base_automation create_base_automation Write create_odoo_model create_odoo_model Write create_odoo_module create_odoo_module Write create_odoo_view create_odoo_view Write create_owl_client_action Generate an Odoo OWL client action scaffold and matching ir.actions.client XML. Write create_owl_component Generate an Odoo OWL component scaffold with JS, XML, SCSS, and manifest assets. Write create_owl_field_widget Generate an Odoo OWL field widget scaffold using standardFieldProps. Write create_owl_service Generate an Odoo frontend service scaffold for the services registry.

All 25 Odoo Dev MCP tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about search_documentation

What does the search_documentation tool do? +

search_documentation. 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 search_documentation? +

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

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

Can I rate-limit search_documentation? +

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

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

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

CHECK YOUR STACK →