unifi_get_route_details
Get detailed information about a specific static route by its ID
This record as markdown: /tools/io-github-sirkirby-unifi-access-mcp/unifi-get-route-details.md
What unifi_get_route_details does on UniFi Access MCP
AI agents call unifi_get_route_details 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_route_details is rated Low
This tool retrieves static route configuration details without creating, modifying, deleting, or executing any changes. It is a read-only information retrieval operation that poses minimal security risk, suitable for configuration review and auditing purposes.
From the tool's definition Tool name includes 'get' and description states 'Get detailed information about a specific static route by its ID' - a pure query operation with no modification or execution capabilities.
Attacks that exploit this kind of access
The rule that runs unifi_get_route_details 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_route_details, this is the rule to start with:
unifi_get_route_details 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_route_details call is checked against it from then on.
Questions about unifi_get_route_details
Get detailed information about a specific static route by its ID. 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_route_details: 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_route_details 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_route_details 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_route_details. 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_route_details 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