Skip to main content
Glama
nntkio

UniFi MCP Server

by nntkio

block_client

Block network access for a specific device by its MAC address to restrict unauthorized connections.

Instructions

Block a client from accessing the network

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
macYesMAC address of the client to block

Implementation Reference

  • The execution logic for the block_client tool within the unified call_tool handler.
    case "block_client":
        mac = arguments.get("mac", "")
        await client.block_client(mac)
        return [
            TextContent(
                type="text",
                text=f"Client {mac} has been blocked from the network.",
            )
        ]
  • Input schema and metadata for the block_client tool, defined in list_tools().
    Tool(
        name="block_client",
        description="Block a client from accessing the network",
        inputSchema={
            "type": "object",
            "properties": {
                "mac": {
                    "type": "string",
                    "description": "MAC address of the client to block",
                }
            },
            "required": ["mac"],
        },
    ),
  • Decorators registering the tool list and call handlers for all tools including block_client.
    @server.list_tools()
    async def list_tools() -> list[Tool]:
        """List all available UniFi MCP tools."""
        return [
            # Device tools
            Tool(
                name="get_devices",
                description="Get all UniFi network devices (access points, switches, gateways)",
                inputSchema={
                    "type": "object",
                    "properties": {},
                    "required": [],
                },
            ),
            Tool(
                name="restart_device",
                description="Restart a UniFi network device by its MAC address",
                inputSchema={
                    "type": "object",
                    "properties": {
                        "mac": {
                            "type": "string",
                            "description": "MAC address of the device to restart (e.g., '00:11:22:33:44:55')",
                        }
                    },
                    "required": ["mac"],
                },
            ),
            # Client tools
            Tool(
                name="get_clients",
                description="Get all currently connected clients on the UniFi network",
                inputSchema={
                    "type": "object",
                    "properties": {
                        "include_offline": {
                            "type": "boolean",
                            "description": "Include offline/historical clients",
                            "default": False,
                        }
                    },
                    "required": [],
                },
            ),
            Tool(
                name="block_client",
                description="Block a client from accessing the network",
                inputSchema={
                    "type": "object",
                    "properties": {
                        "mac": {
                            "type": "string",
                            "description": "MAC address of the client to block",
                        }
                    },
                    "required": ["mac"],
                },
            ),
            Tool(
                name="unblock_client",
                description="Unblock a previously blocked client",
                inputSchema={
                    "type": "object",
                    "properties": {
                        "mac": {
                            "type": "string",
                            "description": "MAC address of the client to unblock",
                        }
                    },
                    "required": ["mac"],
                },
            ),
            Tool(
                name="disconnect_client",
                description="Force disconnect a client from the network",
                inputSchema={
                    "type": "object",
                    "properties": {
                        "mac": {
                            "type": "string",
                            "description": "MAC address of the client to disconnect",
                        }
                    },
                    "required": ["mac"],
                },
            ),
            # Site tools
            Tool(
                name="get_sites",
                description="Get all UniFi sites configured on the controller",
                inputSchema={
                    "type": "object",
                    "properties": {},
                    "required": [],
                },
            ),
            Tool(
                name="get_site_health",
                description="Get health status for the current site",
                inputSchema={
                    "type": "object",
                    "properties": {},
                    "required": [],
                },
            ),
            Tool(
                name="get_networks",
                description="Get all network configurations for the current site",
                inputSchema={
                    "type": "object",
                    "properties": {},
                    "required": [],
                },
            ),
            # Activity tools
            Tool(
                name="get_device_activity",
                description="Get activity for a specific device including connected clients and their traffic",
                inputSchema={
                    "type": "object",
                    "properties": {
                        "mac": {
                            "type": "string",
                            "description": "MAC address of the device (AP or switch)",
                        }
                    },
                    "required": ["mac"],
                },
            ),
        ]
    
    
    @server.call_tool()
    async def call_tool(name: str, arguments: dict[str, Any]) -> list[TextContent]:
  • Underlying UniFiClient method that performs the actual API call to block the client.
    async def block_client(self, mac: str) -> bool:
        """Block a client from the network.
    
        Args:
            mac: Client MAC address.
    
        Returns:
            True if block command was sent successfully.
        """
        await self._request(
            "POST",
            "/api/s/{site}/cmd/stamgr",
            json={"cmd": "block-sta", "mac": mac.lower()},
        )
        return True
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. While it indicates a destructive action ('Block'), it doesn't specify whether this is permanent or temporary, what permissions are required, whether it affects other network services, or what the expected outcome looks like. This leaves significant gaps for a mutation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that directly states the tool's purpose with no wasted words. It's appropriately sized and front-loaded, making it easy to understand immediately.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive mutation tool with no annotations and no output schema, the description is insufficient. It doesn't explain what 'blocking' entails operationally, what happens to the client, whether the action is reversible, or what confirmation/response to expect. More context is needed given the tool's complexity and lack of structured metadata.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% description coverage, with the single parameter 'mac' clearly documented. The description doesn't add any additional parameter context beyond what the schema provides, so it meets the baseline for high schema coverage without compensating value.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Block') and target ('client from accessing the network'), providing a specific verb+resource combination. However, it doesn't explicitly distinguish this from its sibling 'disconnect_client' or 'unblock_client', which would be needed for a perfect score.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided about when to use this tool versus alternatives like 'disconnect_client' or 'unblock_client'. The description states what it does but offers no context about appropriate use cases, prerequisites, or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/nntkio/unifiMCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server