getAllRoles

[DEPRECATED] Use getUserRoleProfile instead. Same GET /roles endpoint. Get all user roles configured on the controller.

SERVERTplink Omada SOURCEmigueltvms/tplink-omada-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade C, identity unverified Pull the record →

This record as markdown: /tools/migueltvms-tplink-omada-mcp/getallroles.md

WHAT IT DOES

What getAllRoles does on Tplink Omada

AI agents call getAllRoles 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.

RISK

Why getAllRoles is rated Low

This tool retrieves role configuration data from the TP-Link Omada controller without modifying, deleting, or executing operations. The deprecated status and reference to a replacement tool (getUserRoleProfile) further confirm it is a simple data retrieval endpoint. Risk is low as it only exposes existing role definitions without capability to change them or impact network operations.

From the tool's definition Tool description states 'Get all user roles configured on the controller' with GET method, indicating a read-only query operation with no side effects.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs getAllRoles 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 getAllRoles, this is the rule to start with:

getAllRoles Allowed

getAllRoles is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "getAllRoles": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Tplink Omada, apply this rule, and every getAllRoles call is checked against it from then on.

FAQ

Questions about getAllRoles

What does the getAllRoles tool do? +

[DEPRECATED] Use getUserRoleProfile instead. Same GET /roles endpoint. Get all user roles configured on the controller. It is categorised as a Read tool in the Tplink Omada MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on getAllRoles? +

Register the Tplink Omada MCP server in PolicyLayer and add a rule for getAllRoles: 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.

What risk level is getAllRoles? +

getAllRoles is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit getAllRoles? +

Yes. Add a rate_limit block to the getAllRoles 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.

How do I block getAllRoles completely? +

Set action: deny in the PolicyLayer policy for getAllRoles. 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.

What MCP server provides getAllRoles? +

getAllRoles 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.

KEEP EXPLORING

More on Tplink Omada, and thousands of servers like it.

This server

All 327 Tplink Omada tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →