listSiteAuditLogs
List admin audit logs for a site: who made what configuration change and when. Returns username, action description, source IP, and timestamp. Useful for tracking config changes or troubleshooting who changed what.
This record as markdown: /tools/migueltvms-tplink-omada-mcp/listsiteauditlogs.md
What listSiteAuditLogs does on Tplink Omada
AI agents call listSiteAuditLogs 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 listSiteAuditLogs is rated Low
This tool only reads and retrieves historical audit log information from the TP-Link Omada controller. It does not modify, delete, or execute any configuration changes—it merely reports who made changes and when. While audit logs may contain sensitive operational information, the tool itself performs a straightforward read operation with no side effects, making it a Read category tool with low severity.
From the tool's definition Tool returns audit log data: 'username, action description, source IP, and timestamp'. The description contains passive verbs 'List' and 'Returns', indicating data retrieval with no modification or side effects.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs listSiteAuditLogs 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 listSiteAuditLogs, this is the rule to start with:
listSiteAuditLogs 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 listSiteAuditLogs call is checked against it from then on.
Questions about listSiteAuditLogs
List admin audit logs for a site: who made what configuration change and when. Returns username, action description, source IP, and timestamp. Useful for tracking config changes or troubleshooting who changed what. 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 listSiteAuditLogs: 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.
listSiteAuditLogs 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 listSiteAuditLogs 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 listSiteAuditLogs. 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.
listSiteAuditLogs 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