unifi_get_traffic_flows
A read tool on the UniFi Access MCP server.
This record as markdown: /tools/io-github-sirkirby-unifi-access-mcp/unifi-get-traffic-flows.md
What unifi_get_traffic_flows does on UniFi Access MCP
AI agents call unifi_get_traffic_flows to retrieve information from UniFi Access MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why unifi_get_traffic_flows is rated Low
The 'get_' prefix and absence of any modifying keywords (create, delete, update, execute) indicate this retrieves network traffic data without side effects. Confidence is moderate (0.75) rather than high because the description is empty, leaving some ambiguity about whether this could involve execution of network diagnostics or commands, but the read-oriented naming strongly suggests passive data retrieval.
From the tool's definition Tool name 'unifi_get_traffic_flows' indicates data retrieval ('get') of traffic flow information. No description provided, but naming convention and context alongside sibling tools (access_get_activity_summary, access_get_event, etc.) suggest a query…
Attacks that exploit this kind of access
The rule that runs unifi_get_traffic_flows 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_get_traffic_flows, this is the rule to start with:
unifi_get_traffic_flows is read-only, so it stays allowed. 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_get_traffic_flows call is checked against it from then on.
Questions about unifi_get_traffic_flows
unifi_get_traffic_flows is a read tool on the UniFi Access MCP server. It is categorised as a Read tool in the UniFi Access MCP MCP Server, which means it retrieves data without modifying state.
Register the UniFi Access MCP server in PolicyLayer and add a rule for unifi_get_traffic_flows: 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_get_traffic_flows is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the unifi_get_traffic_flows 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_get_traffic_flows. 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_get_traffic_flows 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