create_device_group_tool · F5 MCP Server MCP: Risk & Policy

WHAT IT DOES

What create_device_group_tool does on F5 MCP Server

AI agents use create_device_group_tool to create or update resources in F5 MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your F5 MCP Server environment.

WHY IT NEEDS A POLICY

Why create_device_group_tool needs a policy

This tool creates a new device group with specific synchronization and save settings on F5 devices. Device groups are critical infrastructure components for HA (High Availability) and cluster management. Creating or modifying device groups affects network architecture and failover behavior, making this a Write operation with high severity due to potential impact on system availability and configuration consistency.

From the tool's definition Tool description states 'device group 생성' (create device group) with configuration of autoSync, saveOnAutoSync, and fullLoadOnSync parameters. The F5 server enables comprehensive management of configurations including creating objects.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_device_group_tool Rate-limited

create_device_group_tool 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_device_group_tool": {
      "limits": [
        {
          "counter": "create_device_group_tool_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches F5 MCP Server, so you can run agents against it safely.

FAQ

Questions about create_device_group_tool

What does the create_device_group_tool tool do? +

device group 생성. 기본: autoSync=enabled, saveOnAutoSync=True(Save on Automatic Sync), fullLoadOnSync=False(Incremental Auto Sync). It is categorised as a Write tool in the F5 MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_device_group_tool? +

Register the F5 MCP Server MCP server in PolicyLayer and add a rule for create_device_group_tool: 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 F5 MCP Server. Nothing to install.

What risk level is create_device_group_tool? +

create_device_group_tool is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit create_device_group_tool? +

Yes. Add a rate_limit block to the create_device_group_tool 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.

How do I block create_device_group_tool completely? +

Set action: deny in the PolicyLayer policy for create_device_group_tool. 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.

What MCP server provides create_device_group_tool? +

create_device_group_tool is provided by the F5 MCP Server MCP server (mink0119/f5-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.