Clone an existing configuration group.
AI agents use clone_group to create or update resources in HPE Aruba Networking Central MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your HPE Aruba Networking Central MCP Server environment.
Cloning a configuration group creates a new group based on an existing one. This is a Write operation (creates new data reversibly). Severity is high because configuration groups in network infrastructure affect potentially many devices and network segments — misconfiguration or unauthorized cloning could propagate bad configurations at scale.
From the tool's definition Clone an existing configuration group
Attacks that exploit this kind of access
Clone an existing configuration group. It is categorised as a Write tool in the HPE Aruba Networking Central MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the HPE Aruba Networking Central MCP Server MCP server in PolicyLayer and add a rule for clone_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 HPE Aruba Networking Central MCP Server. Nothing to install.
clone_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 clone_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 clone_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.
clone_group is provided by the HPE Aruba Networking Central MCP Server MCP server (the-otner/aruba-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 →