search_troubleshooting
Search FortiMonitor documentation for troubleshooting guides,
This record as markdown: /tools/gjenkins20-unofficial-fortimonitor-mcp-server/search-troubleshooting.md
What search_troubleshooting does on Unofficial FortiMonitor MCP Server
AI agents call search_troubleshooting 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 search_troubleshooting is rated Low
This tool retrieves or queries documentation content with no side effects. It is a read-only search operation that does not create, modify, delete, or execute anything. The low severity reflects minimal risk even if misused by an AI agent, as it only returns documentation content.
From the tool's definition Tool name 'search_troubleshooting' and description 'Search FortiMonitor documentation for troubleshooting guides' indicate a search/query operation against documentation without modification or execution capabilities.
Attacks that exploit this kind of access
The rule that runs search_troubleshooting 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 search_troubleshooting, this is the rule to start with:
search_troubleshooting 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 search_troubleshooting call is checked against it from then on.
Questions about search_troubleshooting
Search FortiMonitor documentation for troubleshooting guides,. 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 search_troubleshooting: 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.
search_troubleshooting 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 search_troubleshooting 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 search_troubleshooting. 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.
search_troubleshooting 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