UniFi Network MCP Server

by owine

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

Get ACL rule

unifi_get_acl_rule

Read-only

Fetch a specific UniFi Network ACL rule by site ID and rule ID to view its full match criteria and action.

Instructions

Get a specific ACL rule by ID (full match criteria and action).

Input Schema

Name	Required	Description	Default
`siteId`	Yes	Site ID
`aclRuleId`	Yes	ACL rule ID

Output Schema

Name	Required	Description	Default
`id`	Yes
`name`	No
`type`	No
`index`	No
`action`	No
`enabled`	No
`metadata`	No
`description`	No
`sourceFilter`	No
`protocolFilter`	No
`destinationFilter`	No
`enforcingDeviceFilter`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedv2.15.0Oct 14, 2026
- addedInput schema / properties / aclRuleId / pattern
```
Added value: +"^[A-Za-z0-9_-]{1,64}$"
```
- addedInput schema / properties / siteId / pattern
```
Added value: +"^[A-Za-z0-9_-]{1,64}$"
```
- changedOutput schema / additionalProperties
```
Previous value: -falseNew value: +{}
```
- changedOutput schema / properties / description / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- addedOutput schema / properties / metadata / properties / configurable
```
Added value: +{
+  "type": "boolean"
+}
```
- addedOutput schema / properties / protocolFilter / anyOf
```
Added value: +[
+  {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / protocolFilter / items
```
Removed value: -{
-  "type": "string"
-}
```
- removedOutput schema / properties / protocolFilter / type
```
Removed value: -"array"
```

Changed1 schema field changedv2.13.0Sep 20, 2026

addedOutput schema / properties / index

Added value: +{
+  "maximum": 9007199254740991,
+  "minimum": -9007199254740991,
+  "type": "integer"
+}

Addedv2.10.0Jul 29, 2026
Removedv2.9.0Jul 23, 2026
First observedv2.8.0Jun 30, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered without the description. The parenthetical 'full match criteria and action' adds a small hint about the richness of the returned entity, but with an output schema present this is largely redundant context rather than new behavioral disclosure.

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

Conciseness4/5

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

A single short sentence that is front-loaded with the verb and resource; every clause earns its place. It is arguably under-specified rather than over-long, so not a full 5.

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

Completeness4/5

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

For a simple two-parameter read tool with full schema coverage, complete annotations, and an output schema that carries the return shape, the description covers the essentials. Only the absence of sibling routing (vs. unifi_list_acl_rules / unifi_get_acl_rule_ordering) leaves a minor gap.

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?

Schema description coverage is 100% and both parameters (siteId, aclRuleId) are documented in the schema, so the baseline is 3. The description confirms the ID is the lookup key but adds no format, pattern, or scoping detail beyond the schema.

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?

States a specific verb (Get) and resource (a specific ACL rule) with the lookup key (by ID), which distinguishes it from unifi_list_acl_rules. It does not explicitly name the sibling it is not, so the differentiation is implicit rather than stated.

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?

There is no when-to-use guidance, no prerequisite statement, and no mention of the alternative (unifi_list_acl_rules) for discovering an ID. The 'by ID' phrasing only weakly implies you must already have the identifier.

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

Deploy Server