This record as markdown: /tools/adbutler/delete-demand-source.md
What delete_demand_source does on AdButler
AI agents call delete_demand_source to permanently remove resources in AdButler, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | number | Yes | Demand source ID |
Parameters from the server's own tool schema.
Why delete_demand_source is rated Critical
The tool permanently removes a demand source from the AdButler system. Deletion of advertising infrastructure (demand sources) cannot be undone and represents a destructive action that could disrupt ad serving and revenue flows. While not financial per se, the impact on ad operations is severe.
From the tool's definition Tool name explicitly contains 'delete'; description states 'Delete a demand source'. This is an irreversible data deletion operation.
Attacks that exploit this kind of access
The rule that runs delete_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 delete_demand_source, this is the rule to start with:
delete_demand_source is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect AdButler, apply this rule, and every delete_demand_source call is checked against it from then on.
Questions about delete_demand_source
Delete a demand source. It is categorised as a Destructive tool in the AdButler MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
delete_demand_source 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 delete_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.
delete_demand_source is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_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.
Set action: deny in the PolicyLayer policy for delete_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.
delete_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.
More on AdButler, and thousands of servers like it.
Across the catalogue