get_adom_health

Get health status of ADOM including all managed devices.

SERVERFortimanager SOURCEjmpijll/fortimanager-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/jmpijll-fortimanager-mcp/get-adom-health.md

WHAT IT DOES

What get_adom_health does on Fortimanager

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

RISK

Why get_adom_health is rated Low

This tool queries and retrieves health status information about an ADOM (Administrative Domain) and its managed devices. It performs no modifications, deletions, code execution, or financial operations. The 'get' verb and 'health status' retrieval are characteristic of Read operations. Severity is low because misuse would only expose informational data about system health, not enable destructive or harmful actions.

From the tool's definition Tool name 'get_adom_health' and description 'Get health status of ADOM including all managed devices' indicate a retrieval/query operation with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_adom_health safely

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

get_adom_health Allowed

get_adom_health 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": {
    "get_adom_health": {}
  }
}

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

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

FAQ

Questions about get_adom_health

What does the get_adom_health tool do? +

Get health status of ADOM including all managed devices. It is categorised as a Read tool in the Fortimanager MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_adom_health? +

Register the Fortimanager MCP server in PolicyLayer and add a rule for get_adom_health: 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 Fortimanager. Nothing to install.

What risk level is get_adom_health? +

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

Can I rate-limit get_adom_health? +

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

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

get_adom_health is provided by the Fortimanager MCP server (jmpijll/fortimanager-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Fortimanager, and thousands of servers like it.

This server

All 584 Fortimanager tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

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