unifi_rename_device

Rename a device in the Unifi Network controller by MAC address

SERVERUniFi Access MCP SOURCEpypi:unifi-protect-mcp
Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-sirkirby-unifi-access-mcp/unifi-rename-device.md

What unifi_rename_device does on UniFi Access MCP

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

Why unifi_rename_device is rated Medium

Renaming a device is a reversible modification that changes configuration state but does not delete data or execute arbitrary commands. It fits the Write category. Severity is medium because renaming could cause operational confusion (e.g., if an attacker renames critical network devices to mask their identity or create chaos), but the action itself is easily undone by renaming again.

From the tool's definition Tool description states 'Rename a device in the Unifi Network controller by MAC address' — this modifies device metadata reversibly through a rename operation, which is a write action.

Questions about unifi_rename_device

What does the unifi_rename_device tool do? +

Rename a device in the Unifi Network controller by MAC address. It is categorised as a Write tool in the UniFi Access MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on unifi_rename_device? +

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

What risk level is unifi_rename_device? +

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

Can I rate-limit unifi_rename_device? +

Yes. Add a rate_limit block to the unifi_rename_device 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 unifi_rename_device completely? +

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

unifi_rename_device is provided by the UniFi Access MCP server (pypi:unifi-protect-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on UniFi Access, and thousands of servers like it.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of UniFi Access's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.