unifi_get_traffic_flow_statistics
A read tool on the UniFi Access MCP server.
This record as markdown: /tools/io-github-sirkirby-unifi-access-mcp/unifi-get-traffic-flow-statistics.md
What unifi_get_traffic_flow_statistics does on UniFi Access MCP
AI agents call unifi_get_traffic_flow_statistics 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_flow_statistics is rated Low
The 'get_traffic_flow_statistics' naming convention indicates querying or fetching traffic statistics without modifying any state. The empty description lowers confidence slightly, but the consistent naming pattern across sibling tools and the read-only semantic of 'get' strongly suggest this is a Read operation. No side effects, code execution, data modification, destruction, or financial operations are implied.
From the tool's definition Tool name contains 'get' and 'statistics', indicating a retrieval operation with no description provided. Based on sibling tools which are predominantly read-only (get_activity_summary, get_credential, get_device, get_door, get_door_status, get_event,…
Attacks that exploit this kind of access
The rule that runs unifi_get_traffic_flow_statistics 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_flow_statistics, this is the rule to start with:
unifi_get_traffic_flow_statistics 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_flow_statistics call is checked against it from then on.
Questions about unifi_get_traffic_flow_statistics
unifi_get_traffic_flow_statistics 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_flow_statistics: 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_flow_statistics 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_flow_statistics 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_flow_statistics. 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_flow_statistics 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