AI agents call check_device_connectivity 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 name implies checking or verifying connectivity status of a device, which is a read/query operation with no side effects. However, the empty description lowers confidence. Given the sibling tools context (network device management), this is most likely a diagnostic read operation.
From the tool's definition Tool name 'check_device_connectivity' suggests a read/diagnostic operation; description is empty and uninformative.
Documented attack patterns abuse exactly the kind of access check_device_connectivity 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_device_connectivity:
{
"version": "1",
"default": "deny",
"tools": {
"check_device_connectivity": {}
}
}check_device_connectivity 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_device_connectivity. 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_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.
check_device_connectivity 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_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.
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.
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.
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.