create_device_group · API-Central MCP: Risk & Policy

WHAT IT DOES

What create_device_group does on API-Central

AI agents use create_device_group to create or update resources in API-Central — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your API-Central environment.

WHY IT NEEDS A POLICY

Why create_device_group needs a policy

This tool creates a new device group resource in the HPE Aruba Central network management system, which is a reversible write operation. Device groups are organizational/logical constructs that can be deleted or modified later, so this is not Destructive. It does not execute arbitrary commands, move money, or retrieve data passively.

From the tool's definition The tool description states 'Create a device group', which is a write operation that creates and stores new configuration data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_device_group Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_device_group": {
      "limits": [
        {
          "counter": "create_device_group_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 API-Central, so you can run agents against it safely.

FAQ

Questions about create_device_group

What does the create_device_group tool do? +

Create a device group, optionally pre-populated with device serial numbers. It is categorised as a Write tool in the API-Central 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? +

Register the API-Central MCP server in PolicyLayer and add a rule for create_device_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 API-Central. Nothing to install.

What risk level is create_device_group? +

create_device_group 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? +

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

How do I block create_device_group completely? +

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

What MCP server provides create_device_group? +

create_device_group is provided by the API-Central MCP server (secure-ssid/centralmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.