Move devices to a different group.
AI agents use move_devices 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.
This tool creates or modifies data reversibly by relocating devices between groups. The operation is not destructive (devices are not deleted), not financial, and not code execution. It is a state change that can be undone by moving devices back to their original group.
From the tool's definition Tool name is 'move_devices' and description states it 'Move devices to a different group' — this is a modification of device state/organization within the inventory management system.
Attacks that exploit this kind of access
Move devices to a different 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 move_devices: 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.
move_devices 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 move_devices 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 move_devices. 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.
move_devices 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 →