Low Risk

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.

How to control getAllDeviceBySite ↓

What getAllDeviceBySite does on Tplink Omada

AI agents call getAllDeviceBySite to retrieve information from Tplink Omada without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why getAllDeviceBySite needs a policy

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.

Documented attack patterns abuse exactly the kind of access getAllDeviceBySite gives an agent:

How to control getAllDeviceBySite

PolicyLayer is an MCP gateway — it sits between your AI agents and Tplink Omada, and nothing reaches the server without passing your rules. This is the rule we recommend for getAllDeviceBySite:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "getAllDeviceBySite": {}
  }
}

getAllDeviceBySite is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Tplink Omada — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about getAllDeviceBySite

What does the getAllDeviceBySite tool do? +

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.

How do I enforce a policy on getAllDeviceBySite? +

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.

What risk level is getAllDeviceBySite? +

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

Can I rate-limit getAllDeviceBySite? +

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.

How do I block getAllDeviceBySite completely? +

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.

What MCP server provides getAllDeviceBySite? +

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.

Enforce policy on every Tplink Omada tool call.

Start from Tplink Omada, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

327 Tplink Omada tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.