replace_rich_media_creative_file
Replace the file on a rich media creative
This record as markdown: /tools/adbutler/replace-rich-media-creative-file.md
What replace_rich_media_creative_file does on AdButler
AI agents use replace_rich_media_creative_file 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 |
|---|---|---|---|
id | number | Yes | Creative ID |
Parameters from the server's own tool schema.
Why replace_rich_media_creative_file is rated Medium
This tool modifies data reversibly—replacing a file is an update operation that can be undone by re-uploading a different file. It does not delete data permanently (Destructive), execute arbitrary code (Execute), transfer funds (Financial), or merely read data (Read). The medium severity reflects that incorrect file replacement could disrupt ad campaigns, but the operation is reversible.
From the tool's definition Tool name 'replace_rich_media_creative_file' and description 'Replace the file on a rich media creative' indicate modifying an existing creative asset by replacing its file content.
Attacks that exploit this kind of access
The rule that runs replace_rich_media_creative_file 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 replace_rich_media_creative_file, this is the rule to start with:
replace_rich_media_creative_file stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 replace_rich_media_creative_file call is checked against it from then on.
Questions about replace_rich_media_creative_file
Replace the file on a rich media creative. 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.
replace_rich_media_creative_file 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 replace_rich_media_creative_file: 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.
replace_rich_media_creative_file 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 replace_rich_media_creative_file 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 replace_rich_media_creative_file. 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.
replace_rich_media_creative_file 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