AI agents call check_adom_integrity to retrieve information from Fortimanager without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The term 'check' typically implies a read-only audit or verification operation with no side effects. However, the empty description severely limits confidence in this classification. Given the sibling tools on this server involve policy management, device configuration, and network settings, this tool likely performs a diagnostic check of ADOM (Administrative Domain) integrity in FortiManager without modifying state.
From the tool's definition Tool name 'check_adom_integrity' suggests an integrity verification operation. No description provided to clarify the exact functionality.
Documented attack patterns abuse exactly the kind of access check_adom_integrity gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Fortimanager, and nothing reaches the server without passing your rules. This is the rule we recommend for check_adom_integrity:
{
"version": "1",
"default": "deny",
"tools": {
"check_adom_integrity": {}
}
}check_adom_integrity is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
check_adom_integrity. It is categorised as a Read tool in the Fortimanager MCP Server, which means it retrieves data without modifying state.
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.
check_adom_integrity is a Read tool with low risk. Read-only tools are generally safe to allow by default.
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.
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.
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.
Start from Fortimanager, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
584 Fortimanager tools catalogued and risk-classified — across an index of 43,000+ MCP servers.