create_compound_service
Create a new compound service that aggregates multiple server checks
This record as markdown: /tools/gjenkins20-unofficial-fortimonitor-mcp-server/create-compound-service.md
What create_compound_service does on Unofficial FortiMonitor MCP Server
AI agents use create_compound_service 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 create_compound_service is rated Medium
This tool creates a new entity (compound service) in the monitoring system, which is a reversible write operation. It does not execute arbitrary code, delete data, or move money. The severity is medium because misconfiguration could affect monitoring visibility or alert routing, but the blast radius is limited to the monitoring system's configuration layer.
From the tool's definition Tool name 'create_compound_service' and description 'Create a new compound service that aggregates multiple server checks' indicate creation of a new monitoring configuration object.
Attacks that exploit this kind of access
The rule that runs create_compound_service 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 create_compound_service, this is the rule to start with:
create_compound_service 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 create_compound_service call is checked against it from then on.
Questions about create_compound_service
Create a new compound service that aggregates multiple server checks. 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 create_compound_service: 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.
create_compound_service 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 create_compound_service 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 create_compound_service. 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.
create_compound_service 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