add_servers_to_group
Add one or more servers to an existing server group.
This record as markdown: /tools/gjenkins20-unofficial-fortimonitor-mcp-server/add-servers-to-group.md
What add_servers_to_group does on Unofficial FortiMonitor MCP Server
AI agents use add_servers_to_group to create or update resources in Unofficial FortiMonitor MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Unofficial FortiMonitor MCP Server environment.
Why add_servers_to_group is rated Medium
The tool modifies server group membership by adding servers to groups. This is a write operation that creates or updates relationships but does not execute arbitrary code, trigger external operations beyond group management, delete data, or move money. The severity is medium because misconfiguration could add critical servers to wrong groups or compromise monitoring scope, but the action is reversible.
From the tool's definition Tool name 'add_servers_to_group' and description 'Add one or more servers to an existing server group' indicate creation/modification of group membership relationships. This is a reversible write operation (servers can be removed from groups).
Attacks that exploit this kind of access
The rule that runs add_servers_to_group 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 add_servers_to_group, this is the rule to start with:
add_servers_to_group stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 add_servers_to_group call is checked against it from then on.
Questions about add_servers_to_group
Add one or more servers to an existing server group. It is categorised as a Write tool in the Unofficial FortiMonitor MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Unofficial FortiMonitor MCP Server MCP server in PolicyLayer and add a rule for add_servers_to_group: 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.
add_servers_to_group is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the add_servers_to_group 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 add_servers_to_group. 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.
add_servers_to_group 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