Delete a demand endpoint
AI agents call delete_demand_endpoint 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 endpoint ID |
Parameters from the server's own tool schema.
The tool performs an irreversible data deletion (removing a demand endpoint configuration). Deletion cannot be undone without manual restoration. While the blast radius depends on what demand endpoints are in use, deleting an endpoint could disrupt ad delivery or campaign operations. This is classified as Destructive rather than Write because deletion is not reversible.
From the tool's definition Tool name contains 'delete' and description states 'Delete a demand endpoint' — this is an irreversible deletion operation.
Attacks that exploit this kind of access
Delete a demand endpoint. 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_endpoint 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_endpoint: 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_endpoint 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_endpoint 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_endpoint. 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_endpoint 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →