[DEPRECATED] Use getGridStaticRouting instead. Same GET .../routing/static-routings endpoint. Note: listStaticRoutes aggregates results across all pages, while getGridStaticRouting returns a single paginated page (requires page/pageSize). When migrating, be sure to iterate pages to collect all st...
AI agents call listStaticRoutes 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 is a read-only operation that retrieves existing static routing configuration. It queries network routing rules (destination, next-hop, interface, metric, enabled state) without creating, modifying, executing commands, or deleting data. The deprecation notice and pagination details confirm it is a simple data retrieval endpoint.
From the tool's definition Tool description explicitly states 'List static routing rules' and 'GET .../routing/static-routings endpoint', indicating data retrieval with no modification. The tool aggregates and returns routing configuration information without side effects.
Documented attack patterns abuse exactly the kind of access listStaticRoutes 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 listStaticRoutes:
{
"version": "1",
"default": "deny",
"tools": {
"listStaticRoutes": {}
}
}listStaticRoutes 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 getGridStaticRouting instead. Same GET .../routing/static-routings endpoint. Note: listStaticRoutes aggregates results across all pages, while getGridStaticRouting returns a single paginated page (requires page/pageSize). When migrating, be sure to iterate pages to collect all static routing rules. List static routing rules configured for a site: destination network, next-hop IP, interface, metric, and enabled state. 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 listStaticRoutes: 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.
listStaticRoutes 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 listStaticRoutes 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 listStaticRoutes. 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.
listStaticRoutes 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.