AI agents use create_event_log_upload_config to create or update resources in AdButler — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AdButler environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | — | Configuration name |
format | string | — | Log file format |
enabled | boolean | — | Whether the upload configuration is enabled |
frequency | string | — | Upload frequency (e.g. "daily", "hourly") |
connection_id | number | — | SFTP connection ID to use for upload |
Parameters from the server's own tool schema.
This tool creates (writes) a new configuration entity for event log uploads. Creation is reversible—the configuration can be modified, archived, or deleted later. It does not execute external code, delete data permanently, or move money. The scope is limited to adding a configuration record within the AdButler advertising platform.
From the tool's definition Tool name 'create_event_log_upload_config' and description 'Create a new event log upload configuration' indicate creation of a configuration object.
Attacks that exploit this kind of access
Create a new event log upload configuration. It is categorised as a Write tool in the AdButler MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
create_event_log_upload_config accepts 5 parameters: name, format, enabled, frequency, connection_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 create_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.
create_event_log_upload_config is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_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 create_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.
create_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 →