Delete an event log upload configuration
AI agents call delete_event_log_upload_config to permanently remove resources in AdButler — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | number | Yes | Upload configuration ID |
Parameters from the server's own tool schema.
The tool explicitly performs a delete operation on a configuration record. Deletion is irreversible and cannot be undone, fitting the Destructive category. High severity because losing event log upload configurations could disrupt data collection, reporting, or compliance workflows in an ad management platform. The blast radius is significant if an AI agent accidentally deletes active configurations.
From the tool's definition Tool name contains 'delete' and description states 'Delete an event log upload configuration' — irreversible removal of a configuration object.
Attacks that exploit this kind of access
Delete an event log upload configuration. It is categorised as a Destructive tool in the AdButler MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
delete_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 delete_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.
delete_event_log_upload_config is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_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 delete_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.
delete_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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →