getVpnRouteConfig
[DEPRECATED] Use getGridPolicyRouting instead. Same GET .../routing/policy-routings endpoint. Note: this tool returns a full aggregated list, while getGridPolicyRouting is page-based (page/pageSize). When migrating, implement pagination to retrieve all policy-based routing rules. Get policy-based...
This record as markdown: /tools/migueltvms-tplink-omada-mcp/getvpnrouteconfig.md
What getVpnRouteConfig does on Tplink Omada
AI agents call getVpnRouteConfig to retrieve information from Tplink Omada without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why getVpnRouteConfig is rated Low
This tool queries network routing configuration data and returns results without altering system state or executing commands. The [DEPRECATED] marker and reference to pagination indicate this is a simple data retrieval endpoint. While routing information could theoretically inform network attacks, the tool itself only reads configuration—it does not modify, delete, or execute operations.
From the tool's definition Tool name 'getVpnRouteConfig' and description 'Get policy-based routing rules for a site' indicate a retrieval operation with no modification or execution capability.
Attacks that exploit this kind of access
The rule that runs getVpnRouteConfig safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Tplink Omada, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For getVpnRouteConfig, this is the rule to start with:
getVpnRouteConfig 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 Tplink Omada, apply this rule, and every getVpnRouteConfig call is checked against it from then on.
Questions about getVpnRouteConfig
[DEPRECATED] Use getGridPolicyRouting instead. Same GET .../routing/policy-routings endpoint. Note: this tool returns a full aggregated list, while getGridPolicyRouting is page-based (page/pageSize). When migrating, implement pagination to retrieve all policy-based routing rules. Get policy-based routing rules for a site, including source/destination matching criteria and next-hop gateway assignments. 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 getVpnRouteConfig: 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.
getVpnRouteConfig 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 getVpnRouteConfig 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 getVpnRouteConfig. 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.
getVpnRouteConfig 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.
More on Tplink Omada, and thousands of servers like it.
This server
Across the catalogue