Get historical internet speed test results.
AI agents call get_speedtest_results 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 retrieves historical speedtest data from the UniFi controller. It performs a read-only operation with no capability to modify network configuration, execute commands, delete data, or trigger external actions. The blast radius of misuse is minimal—an attacker could only view historical performance metrics, which does not compromise network security or functionality.
From the tool's definition Tool name 'get_speedtest_results' and description 'Get historical internet speed test results' indicate retrieval of existing data with no modification or side effects.
Documented attack patterns abuse exactly the kind of access get_speedtest_results 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_speedtest_results:
{
"version": "1",
"default": "deny",
"tools": {
"get_speedtest_results": {}
}
}get_speedtest_results 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 historical internet speed test results. 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_speedtest_results: 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_speedtest_results 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_speedtest_results 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_speedtest_results. 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_speedtest_results 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.