getRadiusUserList
List local RADIUS server users (paginated). Returns users configured in the built-in RADIUS server on the site, including username and access permissions.
This record as markdown: /tools/migueltvms-tplink-omada-mcp/getradiususerlist.md
What getRadiusUserList does on Tplink Omada
AI agents call getRadiusUserList 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 getRadiusUserList is rated Low
This tool retrieves information about RADIUS users and their access permissions. It performs a read-only query operation with no side effects—no data is created, modified, deleted, or executed. While the returned data (usernames and permissions) could be sensitive in a security context, the tool itself only observes and returns existing information, making it a Read category risk.
From the tool's definition Tool name 'getRadiusUserList' and description 'List local RADIUS server users (paginated)' indicates a query operation that retrieves and returns user configuration data without modification.
Attacks that exploit this kind of access
The rule that runs getRadiusUserList 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 getRadiusUserList, this is the rule to start with:
getRadiusUserList 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 getRadiusUserList call is checked against it from then on.
Questions about getRadiusUserList
List local RADIUS server users (paginated). Returns users configured in the built-in RADIUS server on the site, including username and access permissions. 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 getRadiusUserList: 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.
getRadiusUserList 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 getRadiusUserList 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 getRadiusUserList. 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.
getRadiusUserList 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