update_media_group · AdButler MCP: Risk & Policy

WHAT IT DOES

What update_media_group does on AdButler

AI agents use update_media_group 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	Media group ID
`name`	string	—	Media group name

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why update_media_group needs a policy

This tool modifies campaign/advertising configuration data within the AdButler system. Updates are reversible and create no external financial obligation or code execution. It falls under Write (creates or modifies data reversibly) rather than Execute or Destructive.

From the tool's definition Tool name 'update_media_group' and description 'Update an existing media group' indicate modification of existing data. The action is reversible (updates are not destructive).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_media_group Rate-limited

update_media_group 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_media_group": {
      "limits": [
        {
          "counter": "update_media_group_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_media_group

What does the update_media_group tool do? +

Update an existing media group. 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_media_group accept? +

update_media_group accepts 2 parameters: id, name. 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_media_group? +

Register the AdButler MCP server in PolicyLayer and add a rule for update_media_group: 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_media_group? +

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

Can I rate-limit update_media_group? +

Yes. Add a rate_limit block to the update_media_group 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_media_group completely? +

Set action: deny in the PolicyLayer policy for update_media_group. 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_media_group? +

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