health_check

Check FortiManager MCP server health and connection status.

SERVERFortiManager MCP Server SOURCErstierli/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/rstierli-fortimanager-mcp/health-check.md

WHAT IT DOES

What health_check does on FortiManager MCP Server

AI agents call health_check to retrieve information from FortiManager MCP Server 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_check is rated Low

This tool retrieves status information about the FortiManager server and MCP connection. It performs no modifications, deletions, code execution, or financial operations. It is a passive diagnostic read operation similar to a health probe or status check, which carries minimal risk if invoked by an AI agent.

From the tool's definition Tool name 'health_check' and description 'Check FortiManager MCP server health and connection status' indicate a diagnostic query operation with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs health_check safely

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

health_check Allowed

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

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

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

FAQ

Questions about health_check

What does the health_check tool do? +

Check FortiManager MCP server health and connection status. It is categorised as a Read tool in the FortiManager MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on health_check? +

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

What risk level is health_check? +

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

Can I rate-limit health_check? +

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

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

health_check is provided by the FortiManager MCP Server MCP server (rstierli/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 MCP Server, and thousands of servers like it.

This server

All 236 FortiManager MCP Server tools →

Across the catalogue

The MCP Attack Database →

Guides

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