get_server_group_details
Get detailed information about a specific server group,
This record as markdown: /tools/gjenkins20-unofficial-fortimonitor-mcp-server/get-server-group-details.md
What get_server_group_details does on Unofficial FortiMonitor MCP Server
AI agents call get_server_group_details 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_server_group_details is rated Low
This is a straightforward read/query operation that retrieves group metadata and configuration details. It has no side effects, does not execute code, does not modify data, and does not incur financial obligations. The blast radius of misuse is minimal—an attacker could gather reconnaissance information but cannot directly harm systems or data through this tool alone.
From the tool's definition Tool name 'get_server_group_details' and description 'Get detailed information about a specific server group' indicate a retrieval operation that queries and returns data without modifying or deleting anything.
Attacks that exploit this kind of access
The rule that runs get_server_group_details 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_server_group_details, this is the rule to start with:
get_server_group_details 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_server_group_details call is checked against it from then on.
Questions about get_server_group_details
Get detailed information about a specific server group,. 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_server_group_details: 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_server_group_details 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_server_group_details 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_server_group_details. 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_server_group_details 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