get_event_log_upload_config
Get details of a specific event log upload configuration
This record as markdown: /tools/adbutler/get-event-log-upload-config.md
What get_event_log_upload_config does on AdButler
AI agents call get_event_log_upload_config 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 configuration ID |
Parameters from the server's own tool schema.
Why get_event_log_upload_config is rated Low
This tool purely retrieves and queries existing event log upload configuration data. It has no side effects, does not execute code, does not modify data, and does not trigger external operations. It is a read-only data retrieval operation with minimal blast radius if misused—at worst, an agent could discover configuration details but cannot change or delete anything.
From the tool's definition Tool name 'get_event_log_upload_config' and description 'Get details of a specific event log upload configuration' both indicate a retrieval operation with the verb 'Get', which retrieves configuration details without modifying or executing anything.
Attacks that exploit this kind of access
The rule that runs get_event_log_upload_config 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_config, this is the rule to start with:
get_event_log_upload_config 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_config call is checked against it from then on.
Questions about get_event_log_upload_config
Get details of a specific event log upload configuration. It is categorised as a Read tool in the AdButler MCP Server, which means it retrieves data without modifying state.
get_event_log_upload_config 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_config: 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_config 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_config 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_config. 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_config 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