get_service_where_used

What get_service_where_used does on Fortimanager

AI agents call get_service_where_used 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.

Why get_service_where_used is rated Low

This tool appears to search for or retrieve usage information about a service within FortiManager, which is a read operation with no destructive or modifying side effects. Severity is medium rather than low because identifying where services are used in a security policy context could reveal sensitive network architecture information that an adversary might exploit, though the tool itself performs no harmful actions.

From the tool's definition Tool name 'get_service_where_used' indicates a query operation that retrieves information about where a service is referenced or used. The 'get_' prefix and absence of modification language strongly suggest a read-only operation.

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

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_service_where_used": {}
  }
}

Questions about get_service_where_used