health_scan

ADMIN: probe every deployed stack, classify

SERVEROdoo Claude MCP SOURCErosenvladimirov/odoo-claude-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/rosenvladimirov-odoo-claude-mcp/health-scan.md

WHAT IT DOES

What health_scan does on Odoo Claude MCP

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

RISK

Why health_scan is rated Low

Probes and classifies deployed stacks; retrieves system state without modification or execution.

From the tool's definition probe every deployed stack, classify

Risk signalsBulk/mass operation — affects multiple targets · Admin/system-level operation

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs health_scan safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Odoo Claude MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For health_scan, this is the rule to start with:

health_scan Allowed

health_scan is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

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

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Odoo Claude MCP, apply this rule, and every health_scan call is checked against it from then on.

FAQ

Questions about health_scan

What does the health_scan tool do? +

ADMIN: probe every deployed stack, classify. It is categorised as a Read tool in the Odoo Claude MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on health_scan? +

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

What risk level is health_scan? +

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

Can I rate-limit health_scan? +

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

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

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

KEEP EXPLORING

More on Odoo Claude, and thousands of servers like it.

This server

All 246 Odoo Claude tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →