get_event_logs
Get event logs for account activity (changes, logins, etc.)
This record as markdown: /tools/adbutler/get-event-logs.md
What get_event_logs does on AdButler
AI agents call get_event_logs to retrieve information from AdButler without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
to | string | — | End date filter |
from | string | — | Start date filter |
log_type | string | Yes | Type of event log to retrieve |
Parameters from the server's own tool schema.
Why get_event_logs is rated Low
This tool only reads and retrieves existing audit/event log data. It has no side effects, does not modify state, and does not execute external operations. The blast radius of misuse is minimal since logs are typically read-only records intended for monitoring and compliance review.
From the tool's definition get_event_logs retrieves event logs for account activity (changes, logins, etc.) - a pure query operation that fetches historical audit data without modifying or executing anything.
Attacks that exploit this kind of access
The rule that runs get_event_logs safely
PolicyLayer is an MCP gateway: it sits between your AI agents and AdButler, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_event_logs, this is the rule to start with:
get_event_logs 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 AdButler, apply this rule, and every get_event_logs call is checked against it from then on.
Questions about get_event_logs
Get event logs for account activity (changes, logins, etc.). It is categorised as a Read tool in the AdButler MCP Server, which means it retrieves data without modifying state.
get_event_logs accepts 3 parameters: to, from, log_type. Required: log_type. The full parameter table on this page comes from the server's own tool schema.
Register the AdButler MCP server in PolicyLayer and add a rule for get_event_logs: 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 AdButler. Nothing to install.
get_event_logs 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 get_event_logs 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 get_event_logs. 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.
get_event_logs is provided by the AdButler MCP server (adbutler/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on AdButler, and thousands of servers like it.
This server
Across the catalogue