List service type profiles (paginated). Returns both predefined and custom service types used in ACL and firewall rules.
AI agents call listServiceType 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 enumerates service type profiles used in ACL and firewall rules. It performs a read-only query operation that retrieves existing configuration data without creating, modifying, or deleting any resources. The pagination suggests it is a simple data retrieval endpoint.
From the tool's definition Tool name is 'listServiceType' and description states it 'List service type profiles (paginated)' with 'Returns both predefined and custom service types'. The verb 'list' and 'returns' indicate data retrieval with no modification or side effects.
Documented attack patterns abuse exactly the kind of access listServiceType 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 listServiceType:
{
"version": "1",
"default": "deny",
"tools": {
"listServiceType": {}
}
}listServiceType 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.
List service type profiles (paginated). Returns both predefined and custom service types used in ACL and firewall rules. 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 listServiceType: 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.
listServiceType 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 listServiceType 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 listServiceType. 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.
listServiceType 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.