create_service_group
AI agents use create_service_group to create or update resources in FortiManager MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your FortiManager MCP Server environment.
Creating a service group modifies firewall policy configuration, which is a reversible write operation affecting network security rules. Empty description lowers confidence slightly, but the context (FortiManager for policy management) and naming convention clearly indicate this creates network service definitions.
From the tool's definition Tool named 'create_service_group' on FortiManager server for 'firewall policy management' and 'network configuration'; the 'create_*' prefix indicates data creation/modification in network security infrastructure.
Attacks that exploit this kind of access
create_service_group. It is categorised as a Write tool in the FortiManager MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the FortiManager MCP Server MCP server in PolicyLayer and add a rule for create_service_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 FortiManager MCP Server. Nothing to install.
create_service_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 create_service_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 create_service_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.
create_service_group is provided by the FortiManager MCP Server MCP server (rstierli/fortimanager-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →