getOsgCustomAclList
Get the custom gateway ACL rules list (paginated). Custom ACLs extend the standard gateway ACL rules with user-defined traffic policies.
This record as markdown: /tools/migueltvms-tplink-omada-mcp/getosgcustomacllist.md
What getOsgCustomAclList does on Tplink Omada
AI agents call getOsgCustomAclList 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 getOsgCustomAclList is rated Low
This tool retrieves and displays existing ACL (Access Control List) rules without creating, modifying, deleting, or executing any network policies. It is a pure query operation with no side effects. While ACL information could theoretically inform a malicious network reconnaissance, the tool itself performs only data retrieval, placing it in the Read category with low severity risk.
From the tool's definition Tool name 'getOsgCustomAclList' and description 'Get the custom gateway ACL rules list (paginated)' indicate a retrieval operation with no modification or destructive action. The verb 'Get' and phrase 'list' are unambiguous read operations.
Attacks that exploit this kind of access
The rule that runs getOsgCustomAclList 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 getOsgCustomAclList, this is the rule to start with:
getOsgCustomAclList 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 getOsgCustomAclList call is checked against it from then on.
Questions about getOsgCustomAclList
Get the custom gateway ACL rules list (paginated). Custom ACLs extend the standard gateway ACL rules with user-defined traffic policies. 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 getOsgCustomAclList: 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.
getOsgCustomAclList 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 getOsgCustomAclList 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 getOsgCustomAclList. 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.
getOsgCustomAclList 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