Get EAP/switch device usage for a specific LAN profile. Returns which devices are using the profile. Requires
AI agents call getLanProfileEsUsage 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 performs a read-only query to retrieve information about which devices use a specific LAN profile. It has no side effects, does not modify data, does not execute code or commands, and does not delete or move resources. The action is purely informational retrieval, placing it in the Read category with low severity due to its limited blast radius if misused.
From the tool's definition Tool name 'getLanProfileEsUsage' and description 'Get EAP/switch device usage for a specific LAN profile. Returns which devices are using the profile' indicate a query operation that retrieves usage information without modifying system state.
Documented attack patterns abuse exactly the kind of access getLanProfileEsUsage 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 getLanProfileEsUsage:
{
"version": "1",
"default": "deny",
"tools": {
"getLanProfileEsUsage": {}
}
}getLanProfileEsUsage 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.
Get EAP/switch device usage for a specific LAN profile. Returns which devices are using the profile. Requires. 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 getLanProfileEsUsage: 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.
getLanProfileEsUsage 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 getLanProfileEsUsage 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 getLanProfileEsUsage. 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.
getLanProfileEsUsage 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.