delete_campaign_assignment

Delete a campaign assignment

Server AdButler adbutler/mcp-server
Category Destructive
Risk class Critical
Parameters 11 required

What delete_campaign_assignment does on AdButler

AI agents call delete_campaign_assignment 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.

ParameterTypeRequiredDescription
id number Yes Campaign assignment ID

Parameters from the server's own tool schema.

Why delete_campaign_assignment needs a policy

The tool performs an irreversible deletion operation on campaign assignment data. Deletion operations cannot be undone and represent permanent data loss. This is more severe than Write (reversible modifications) and meets the definition of Destructive category.

From the tool's definition Tool name contains 'delete' and description states 'Delete a campaign assignment'. This irreversibly removes an assignment record.

Questions about delete_campaign_assignment

What does the delete_campaign_assignment tool do? +

Delete a campaign assignment. 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.

What parameters does delete_campaign_assignment accept? +

delete_campaign_assignment accepts 1 parameter: id. Required: id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on delete_campaign_assignment? +

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

delete_campaign_assignment is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_campaign_assignment? +

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

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

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

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.