check_device_connectivity

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-device-connectivity.md

WHAT IT DOES

What check_device_connectivity does on Fortimanager

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

Despite the empty description limiting confidence, the verb 'check' combined with the context of a FortiManager management server indicates this tool queries device connectivity status rather than modifying, executing, or deleting resources.

From the tool's definition The tool name 'check_device_connectivity' with no description suggests a query or status check operation, typical of Read category tools that verify device state without side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

check_device_connectivity Allowed

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

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

FAQ

Questions about check_device_connectivity

What does the check_device_connectivity tool do? +

check_device_connectivity 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_device_connectivity? +

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

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

Can I rate-limit check_device_connectivity? +

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

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

check_device_connectivity 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 →