unifi_set_client_name · Multi-Tool MCP Server MCP

WHAT IT DOES

What unifi_set_client_name does on Multi-Tool MCP Server

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

WHY IT NEEDS A POLICY

Why unifi_set_client_name needs a policy

This tool modifies network device metadata (client name/alias) but does not delete data, execute arbitrary code, or cause financial impact. The change is reversible — names can be updated again. While it affects network infrastructure, the blast radius is limited to cosmetic/organizational metadata rather than network access control or system stability.

From the tool's definition Tool description states 'Set or update the name/alias for a client' — this modifies client metadata within the UniFi network controller system. The verb 'set or update' indicates a reversible change to existing data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

unifi_set_client_name Rate-limited

unifi_set_client_name 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": {
    "unifi_set_client_name": {
      "limits": [
        {
          "counter": "unifi_set_client_name_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 Multi-Tool MCP Server, so you can run agents against it safely.

FAQ

Questions about unifi_set_client_name

What does the unifi_set_client_name tool do? +

Set or update the name/alias for a client. It is categorised as a Write tool in the Multi-Tool 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 unifi_set_client_name? +

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

What risk level is unifi_set_client_name? +

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

Can I rate-limit unifi_set_client_name? +

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

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

unifi_set_client_name is provided by the Multi-Tool MCP Server MCP server (shawn-falconbury/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.