check_adom_integrity

A read tool on the Fortimanager MCP server.

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/check-adom-integrity.md

WHAT IT DOES

What check_adom_integrity does on Fortimanager

AI agents call check_adom_integrity 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 check_adom_integrity is rated Low

The 'check_' prefix typically indicates diagnostic or read operations that examine but do not modify data. An ADOM (Administrative Domain) integrity check would verify the consistency and state of the domain without side effects. The empty description lowers confidence slightly, but the naming convention and context of managing FortiManager configuration strongly suggest this is a non-destructive read operation.

From the tool's definition Tool name contains 'check' which suggests a diagnostic or validation operation that queries system state without modifying it.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs check_adom_integrity 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 check_adom_integrity, this is the rule to start with:

check_adom_integrity Allowed

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

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 check_adom_integrity call is checked against it from then on.

FAQ

Questions about check_adom_integrity

What does the check_adom_integrity tool do? +

check_adom_integrity is a read tool on the Fortimanager MCP server. 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 check_adom_integrity? +

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

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

Can I rate-limit check_adom_integrity? +

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

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

check_adom_integrity 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

The MCP Attack Database →

Guides

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