get_event_log_upload_log
Get details of a specific event log upload log entry
This record as markdown: /tools/adbutler/get-event-log-upload-log.md
What get_event_log_upload_log does on AdButler
AI agents call get_event_log_upload_log 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 |
|---|---|---|---|
id | number | Yes | Upload log ID |
Parameters from the server's own tool schema.
Why get_event_log_upload_log is rated Low
This tool retrieves historical event log data without side effects. It performs a query operation to fetch existing log information, which is non-destructive and does not modify system state. The 'get' verb combined with 'details' confirms read-only access to audit/event log records.
From the tool's definition Tool name 'get_event_log_upload_log' with description 'Get details of a specific event log upload log entry' — 'get' and 'details' indicate retrieval only, no modification or deletion.
Attacks that exploit this kind of access
The rule that runs get_event_log_upload_log 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_log_upload_log, this is the rule to start with:
get_event_log_upload_log 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_log_upload_log call is checked against it from then on.
Questions about get_event_log_upload_log
Get details of a specific event log upload log entry. It is categorised as a Read tool in the AdButler MCP Server, which means it retrieves data without modifying state.
get_event_log_upload_log accepts 1 parameter: id. Required: id. 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_log_upload_log: 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_log_upload_log 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_log_upload_log 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_log_upload_log. 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_log_upload_log 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