update_audio_creative · AdButler MCP: Risk & Policy

WHAT IT DOES

What update_audio_creative does on AdButler

AI agents use update_audio_creative 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.

PARAMETERS

Parameter	Type	Required	Description
`id`	number	Yes	Creative ID
`name`	string	—	Creative name
`description`	string	—	Creative description

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why update_audio_creative needs a policy

This tool modifies an existing audio creative asset within the AdButler ad management system. Updates are reversible (the previous version could be restored), and the blast radius is limited to the affected creative asset. This makes it a Write operation rather than Execute or Destructive.

From the tool's definition Tool name is 'update_audio_creative' and description states 'Update an existing audio creative'. The verb 'update' indicates modification of existing data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_audio_creative Rate-limited

update_audio_creative 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_audio_creative": {
      "limits": [
        {
          "counter": "update_audio_creative_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches AdButler, so you can run agents against it safely.

FAQ

Questions about update_audio_creative

What does the update_audio_creative tool do? +

Update an existing audio 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.

What parameters does update_audio_creative accept? +

update_audio_creative accepts 3 parameters: id, name, description. Required: id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on update_audio_creative? +

Register the AdButler MCP server in PolicyLayer and add a rule for update_audio_creative: 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.

What risk level is update_audio_creative? +

update_audio_creative is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_audio_creative? +

Yes. Add a rate_limit block to the update_audio_creative 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.

How do I block update_audio_creative completely? +

Set action: deny in the PolicyLayer policy for update_audio_creative. 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.

What MCP server provides update_audio_creative? +

update_audio_creative 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.