get_path_monitoring_results
Get the results/data for a specific path monitoring configuration.
This record as markdown: /tools/gjenkins20-unofficial-fortimonitor-mcp-server/get-path-monitoring-results.md
What get_path_monitoring_results does on Unofficial FortiMonitor MCP Server
AI agents call get_path_monitoring_results 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 get_path_monitoring_results is rated Low
This tool queries and retrieves existing monitoring results and configuration data. There is no indication of data modification, deletion, code execution, or financial impact. The blast radius of misuse is limited to information disclosure of monitoring metrics, which poses low risk in a monitoring platform context.
From the tool's definition Tool name 'get_path_monitoring_results' and description 'Get the results/data for a specific path monitoring configuration' indicate retrieval of monitoring data without modification or execution.
Attacks that exploit this kind of access
The rule that runs get_path_monitoring_results 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 get_path_monitoring_results, this is the rule to start with:
get_path_monitoring_results 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 get_path_monitoring_results call is checked against it from then on.
Questions about get_path_monitoring_results
Get the results/data for a specific path monitoring configuration. 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 get_path_monitoring_results: 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.
get_path_monitoring_results 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 get_path_monitoring_results 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 get_path_monitoring_results. 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.
get_path_monitoring_results 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