update_product_source · AdButler MCP: Risk & Policy

WHAT IT DOES

What update_product_source does on AdButler

AI agents use update_product_source 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
`url`	string	—	Source URL
`name`	string	—	Source name
`type`	string	—	Source type
`source_id`	number	Yes	Source ID
`publisher_id`	number	Yes	Publisher ID

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why update_product_source needs a policy

This tool creates or modifies data reversibly. It updates a product source configuration, which is a write operation. The severity is medium because misuse could alter ad campaign configurations affecting ad delivery and reporting, but changes are typically reversible (can be updated again).

From the tool's definition Tool name 'update_product_source' and description 'Update an existing product source' indicate modification of existing data.

Risk signalsAccepts URL/endpoint input (url)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_product_source Rate-limited

update_product_source 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_product_source": {
      "limits": [
        {
          "counter": "update_product_source_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_product_source

What does the update_product_source tool do? +

Update an existing product source. 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_product_source accept? +

update_product_source accepts 5 parameters: url, name, type, source_id, publisher_id. Required: source_id, publisher_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on update_product_source? +

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

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

Can I rate-limit update_product_source? +

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

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

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