unifi_create_route
A other tool on the UniFi Access MCP server.
This record as markdown: /tools/io-github-sirkirby-unifi-access-mcp/unifi-create-route.md
What unifi_create_route does on UniFi Access MCP
AI agents call unifi_create_route as a supporting operation in UniFi Access MCP workflows.
Why unifi_create_route is rated Low
The description is empty and uninformative, making classification uncertain. The tool name suggests a Write action (create), but it doesn't fit the server's stated purpose of managing UniFi Access doors, credentials, policies, visitors, and events. Without further evidence, confidence is very low. Defaulting to Other due to ambiguity.
From the tool's definition Tool name is 'unifi_create_route' but description is empty. The name suggests creating a network route, which is a Write operation, but this is an Access management server focused on doors/credentials/visitors.
Attacks that exploit this kind of access
The rule that runs unifi_create_route 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_route, this is the rule to start with:
unifi_create_route gets a rate cap, and 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_route call is checked against it from then on.
Questions about unifi_create_route
unifi_create_route is a other tool on the UniFi Access MCP server. It is categorised as a Other tool in the UniFi Access MCP MCP Server, which means it performs auxiliary operations.
Register the UniFi Access MCP server in PolicyLayer and add a rule for unifi_create_route: 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_route is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the unifi_create_route 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_route. 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_route 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