getLanProfileEsUsage
Get EAP/switch device usage for a specific LAN profile. Returns which devices are using the profile. Requires
This record as markdown: /tools/migueltvms-tplink-omada-mcp/getlanprofileesusage.md
What getLanProfileEsUsage does on Tplink Omada
AI agents call getLanProfileEsUsage 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 getLanProfileEsUsage is rated Low
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.
Attacks that exploit this kind of access
The rule that runs getLanProfileEsUsage 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 getLanProfileEsUsage, this is the rule to start with:
getLanProfileEsUsage 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 getLanProfileEsUsage call is checked against it from then on.
Questions about getLanProfileEsUsage
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.
More on Tplink Omada, and thousands of servers like it.
This server
Across the catalogue