Low Risk

get_dpi_stats

Get Deep Packet Inspection (DPI) statistics.

How to control get_dpi_stats ↓

What get_dpi_stats does on UniFi MCP

AI agents call get_dpi_stats to retrieve information from UniFi MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_dpi_stats needs a policy

This tool retrieves monitoring and analytics data (DPI statistics) from the UniFi controller without modifying, deleting, or executing any operations. It is purely informational. Read operations have minimal security risk as they do not alter system state.

From the tool's definition Tool name is 'get_dpi_stats' with description 'Get Deep Packet Inspection (DPI) statistics.' The verb 'get' and the action of retrieving statistics indicate a read-only query operation with no side effects.

Documented attack patterns abuse exactly the kind of access get_dpi_stats gives an agent:

How to control get_dpi_stats

PolicyLayer is an MCP gateway — it sits between your AI agents and UniFi MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_dpi_stats:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_dpi_stats": {}
  }
}

get_dpi_stats is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register UniFi MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_dpi_stats

What does the get_dpi_stats tool do? +

Get Deep Packet Inspection (DPI) statistics. It is categorised as a Read tool in the UniFi MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_dpi_stats? +

Register the UniFi MCP server in PolicyLayer and add a rule for get_dpi_stats: 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 MCP. Nothing to install.

What risk level is get_dpi_stats? +

get_dpi_stats is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_dpi_stats? +

Yes. Add a rate_limit block to the get_dpi_stats 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.

How do I block get_dpi_stats completely? +

Set action: deny in the PolicyLayer policy for get_dpi_stats. 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.

What MCP server provides get_dpi_stats? +

get_dpi_stats is provided by the UniFi MCP server (jmagar/unifi-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every UniFi MCP tool call.

Start from UniFi MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

29 UniFi MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.