list_monitoring_nodes
List all monitoring nodes in FortiMonitor. Monitoring nodes are
This record as markdown: /tools/gjenkins20-unofficial-fortimonitor-mcp-server/list-monitoring-nodes.md
What list_monitoring_nodes does on Unofficial FortiMonitor MCP Server
AI agents call list_monitoring_nodes to retrieve information from Unofficial FortiMonitor MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_monitoring_nodes is rated Low
This tool retrieves and enumerates monitoring nodes from the FortiMonitor API. It performs a query operation without modifying, deleting, executing, or creating any resources. The action is informational only, making it a Read category tool.
From the tool's definition Tool name 'list_monitoring_nodes' with description beginning 'List all monitoring nodes in FortiMonitor.' The verb 'list' is a data retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs list_monitoring_nodes safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Unofficial FortiMonitor MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_monitoring_nodes, this is the rule to start with:
list_monitoring_nodes is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Unofficial FortiMonitor MCP Server, apply this rule, and every list_monitoring_nodes call is checked against it from then on.
Questions about list_monitoring_nodes
List all monitoring nodes in FortiMonitor. Monitoring nodes are. It is categorised as a Read tool in the Unofficial FortiMonitor MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Unofficial FortiMonitor MCP Server MCP server in PolicyLayer and add a rule for list_monitoring_nodes: 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 Unofficial FortiMonitor MCP Server. Nothing to install.
list_monitoring_nodes 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 list_monitoring_nodes 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 list_monitoring_nodes. 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.
list_monitoring_nodes is provided by the Unofficial FortiMonitor MCP Server MCP server (gjenkins20/unofficial-fortimonitor-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Unofficial FortiMonitor MCP Server, and thousands of servers like it.
Across the catalogue