update_demand_source

Update an existing demand source

SERVERAdButler SOURCEadbutler/mcp-server

Medium RISK CLASS

Category Write

Parameters 71 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/adbutler/update-demand-source.md

WHAT IT DOES

What update_demand_source does on AdButler

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

Parameter	Type	Required	Description
`id`	number	Yes	Demand source ID
`name`	string	—	Demand source name
`status`	string	—	Whether to send bid requests
`spend_limit`	number	—	Spend limit amount
`spend_limit_end`	string	—	Spend limit end date (ISO-8601)
`spend_limit_start`	string	—	Spend limit start date (ISO-8601)
`spend_limit_period`	string	—	Spend limit reset interval

Parameters from the server's own tool schema.

RISK

Why update_demand_source is rated Medium

This tool creates or modifies data (a demand source configuration) in a reversible manner. It does not delete data (Destructive), execute arbitrary code (Execute), move money (Financial), or retrieve data without side effects (Read). Update operations are classified as Write.

From the tool's definition Tool name 'update_demand_source' and description 'Update an existing demand source' indicate modification of existing data. The 'update' verb and context within an ad management system (AdButler) confirm this is a Write operation that modifies configuration.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs update_demand_source 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 update_demand_source, this is the rule to start with:

update_demand_source Rate-limited

update_demand_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_demand_source": {
      "limits": [
        {
          "counter": "update_demand_source_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect AdButler, apply this rule, and every update_demand_source call is checked against it from then on.

FAQ

Questions about update_demand_source

What does the update_demand_source tool do? +

Update an existing demand 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_demand_source accept? +

update_demand_source accepts 7 parameters: id, name, status, spend_limit, spend_limit_end, spend_limit_start, spend_limit_period. 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_demand_source? +

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

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

Can I rate-limit update_demand_source? +

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

Set action: deny in the PolicyLayer policy for update_demand_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_demand_source? +

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

KEEP EXPLORING

More on AdButler, and thousands of servers like it.

This server

All 622 AdButler tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP →team_manager_update_budget on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →