Get controller system information and status.
AI agents call get_controller_status 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.
This tool queries and returns controller metadata and status information. It performs no writes, deletions, code execution, or financial operations. The blast radius of misuse is minimal—an attacker would only gain visibility into system state, which does not compromise confidentiality of sensitive credentials or enable account takeover on its own. Classified as Read/low severity.
From the tool's definition Tool name 'get_controller_status' and description 'Get controller system information and status' indicate a read-only retrieval operation with no modification or side effects.
Documented attack patterns abuse exactly the kind of access get_controller_status gives an agent:
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_controller_status:
{
"version": "1",
"default": "deny",
"tools": {
"get_controller_status": {}
}
}get_controller_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get controller system information and status. It is categorised as a Read tool in the UniFi MCP MCP Server, which means it retrieves data without modifying state.
Register the UniFi MCP server in PolicyLayer and add a rule for get_controller_status: 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.
get_controller_status 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 get_controller_status 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 get_controller_status. 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.
get_controller_status 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.
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.