Low Risk

getBackupFileList

Get the list of available controller backup files.

How to control getBackupFileList ↓

What getBackupFileList does on Tplink Omada

AI agents call getBackupFileList 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 getBackupFileList needs a policy

This tool performs a read-only query to enumerate backup files. It has no side effects, does not execute code or commands, does not modify data, and does not delete or move resources. The blast radius is minimal—an AI agent listing backups cannot cause harm. Confidence is high because the description is clear and unambiguous.

From the tool's definition Tool name 'getBackupFileList' and description 'Get the list of available controller backup files' indicate a retrieval operation that queries existing backup data without modification or execution.

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

How to control getBackupFileList

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 getBackupFileList:

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

getBackupFileList 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 getBackupFileList

What does the getBackupFileList tool do? +

Get the list of available controller backup files. 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 getBackupFileList? +

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

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

Can I rate-limit getBackupFileList? +

Yes. Add a rate_limit block to the getBackupFileList 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 getBackupFileList completely? +

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

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