Get global audit logs (paginated). Records all administrative operations across the controller. Supports optional filters by result, level, type, and time range.
AI agents call getAuditLogsForGlobal 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.
This tool only fetches audit log records from the controller. It has no side effects and does not modify any data. The severity is low because misuse only exposes administrative activity logs, though these could reveal sensitive operational details.
From the tool's definition 'Get global audit logs (paginated)' and 'Records all administrative operations across the controller' — purely a retrieval/query operation with filtering
Risk signalsAdmin/system-level operation
Documented attack patterns abuse exactly the kind of access getAuditLogsForGlobal gives an agent:
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 getAuditLogsForGlobal:
{
"version": "1",
"default": "deny",
"tools": {
"getAuditLogsForGlobal": {}
}
}getAuditLogsForGlobal is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get global audit logs (paginated). Records all administrative operations across the controller. Supports optional filters by result, level, type, and time range. 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 getAuditLogsForGlobal: 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.
getAuditLogsForGlobal 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 getAuditLogsForGlobal 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 getAuditLogsForGlobal. 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.
getAuditLogsForGlobal 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.
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.