getAllDeviceBySite
Get all devices in a site including offline and disconnected devices. Unlike listDevices which may filter to active-only, this returns the full device inventory. Useful for auditing what hardware is registered to a site.
This record as markdown: /tools/migueltvms-tplink-omada-mcp/getalldevicebysite.md
What getAllDeviceBySite does on Tplink Omada
AI agents call getAllDeviceBySite 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 getAllDeviceBySite is rated Low
This tool queries and retrieves device information from a TP-Link Omada site. It performs a read-only operation that returns data about registered hardware with no side effects, modifications, or external actions triggered. The appropriate classification is Read.
From the tool's definition Tool returns device inventory data ('Get all devices in a site'). Description emphasizes retrieval for auditing purposes with no modification, deletion, or execution mentioned.
Attacks that exploit this kind of access
The rule that runs getAllDeviceBySite 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 getAllDeviceBySite, this is the rule to start with:
getAllDeviceBySite 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 getAllDeviceBySite call is checked against it from then on.
Questions about getAllDeviceBySite
Get all devices in a site including offline and disconnected devices. Unlike listDevices which may filter to active-only, this returns the full device inventory. Useful for auditing what hardware is registered to a site. 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 getAllDeviceBySite: 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.
getAllDeviceBySite 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 getAllDeviceBySite 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 getAllDeviceBySite. 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.
getAllDeviceBySite 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