unifi_create_qos_rule
Create a new QoS rule on the Unifi Network controller. Requires confirmation.
This record as markdown: /tools/io-github-sirkirby-unifi-access-mcp/unifi-create-qos-rule.md
What unifi_create_qos_rule does on UniFi Access MCP
AI agents use unifi_create_qos_rule 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_create_qos_rule is rated Medium
Creating a QoS (Quality of Service) rule is a write operation that modifies network traffic policies. It creates new configuration data but doesn't irreversibly delete or destroy anything. While it affects network behavior and could impact service quality if misconfigured, the reversibility (can be modified or deleted) and the confirmation requirement place it in the Write category rather than Execute or Destructive.
From the tool's definition Tool description states 'Create a new QoS rule' - this is a data creation operation that modifies network configuration. The phrase 'Requires confirmation' indicates it's a reversible write operation rather than destructive.
Attacks that exploit this kind of access
The rule that runs unifi_create_qos_rule safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UniFi Access MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For unifi_create_qos_rule, this is the rule to start with:
unifi_create_qos_rule 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.
The button opens the PolicyLayer dashboard: create your workspace, connect UniFi Access MCP, apply this rule, and every unifi_create_qos_rule call is checked against it from then on.
Questions about unifi_create_qos_rule
Create a new QoS rule on the Unifi Network controller. Requires confirmation. 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.
Register the UniFi Access MCP server in PolicyLayer and add a rule for unifi_create_qos_rule: 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.
unifi_create_qos_rule 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 unifi_create_qos_rule 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 unifi_create_qos_rule. 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.
unifi_create_qos_rule 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.
This server
Across the catalogue