[DEPRECATED] Use getGridPolicyRouting instead. Note: listPolicyRoutes returns an aggregated array of all policy routes, while getGridPolicyRouting is paginated and returns a single page payload (same underlying endpoint). When migrating, implement pagination to retrieve all rules. List policy rou...
AI agents call listPolicyRoutes to retrieve information from Tplink Omada without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays existing policy routing rules without creating, modifying, deleting, or executing them. It is informational only, presenting network configuration data to the user. Even though network policies are security-sensitive, reading them poses minimal risk compared to modifying or executing them. The deprecation note confirms this is a query endpoint that returns aggregated data.
From the tool's definition Tool name is 'listPolicyRoutes' and description states it 'List policy routing rules for the site gateway.' The description contains no language indicating modification, deletion, or execution of arbitrary operations—it is purely a retrieval/query operation.
Documented attack patterns abuse exactly the kind of access listPolicyRoutes gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Tplink Omada, and nothing reaches the server without passing your rules. This is the rule we recommend for listPolicyRoutes:
{
"version": "1",
"default": "deny",
"tools": {
"listPolicyRoutes": {}
}
}listPolicyRoutes 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.
[DEPRECATED] Use getGridPolicyRouting instead. Note: listPolicyRoutes returns an aggregated array of all policy routes, while getGridPolicyRouting is paginated and returns a single page payload (same underlying endpoint). When migrating, implement pagination to retrieve all rules. List policy routing rules for the site gateway. Policy routes direct traffic based on source IP, destination, or protocol — useful for multi-WAN environments. It is categorised as a Read tool in the Tplink Omada MCP Server, which means it retrieves data without modifying state.
Register the Tplink Omada MCP server in PolicyLayer and add a rule for listPolicyRoutes: 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 Tplink Omada. Nothing to install.
listPolicyRoutes 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 listPolicyRoutes 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 listPolicyRoutes. 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.
listPolicyRoutes is provided by the Tplink Omada MCP server (migueltvms/tplink-omada-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Tplink Omada, 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.
327 Tplink Omada tools catalogued and risk-classified — across an index of 43,000+ MCP servers.