Get webhook dispatch logs (paginated). Requires webhookId and a time range in epoch milliseconds. Returns delivery attempts and their status.
AI agents call getWebhookLogsForGlobal 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 queries and retrieves existing webhook log data based on webhookId and time range parameters. It has no side effects—it does not create, modify, delete, execute code, or commit financial obligations. The blast radius of misuse is minimal: an attacker could enumerate webhook activity history, but cannot alter logs, trigger webhooks, or affect system operations.
From the tool's definition Tool name and description indicate retrieval of webhook dispatch logs with pagination. The function 'Get webhook dispatch logs' is a pure read operation that retrieves historical delivery attempt records and their status without modifying any data.
Documented attack patterns abuse exactly the kind of access getWebhookLogsForGlobal 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 getWebhookLogsForGlobal:
{
"version": "1",
"default": "deny",
"tools": {
"getWebhookLogsForGlobal": {}
}
}getWebhookLogsForGlobal 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 webhook dispatch logs (paginated). Requires webhookId and a time range in epoch milliseconds. Returns delivery attempts and their status. 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 getWebhookLogsForGlobal: 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.
getWebhookLogsForGlobal 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 getWebhookLogsForGlobal 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 getWebhookLogsForGlobal. 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.
getWebhookLogsForGlobal 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.