delete_postal_code_target

Delete a postal code target

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

What delete_postal_code_target does on AdButler

AI agents call delete_postal_code_target 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 Postal code target ID

Parameters from the server's own tool schema.

Why delete_postal_code_target needs a policy

The tool performs an irreversible deletion of postal code targeting configuration. While the blast radius is limited to advertising targeting metadata (not financial transactions or user data deletion), it represents permanent data loss that cannot be undone. This makes it Destructive rather than Write.

From the tool's definition Tool name explicitly states 'delete' and description confirms 'Delete a postal code target'. This is an irreversible deletion operation that removes targeting data from an advertising campaign.

Questions about delete_postal_code_target

What does the delete_postal_code_target tool do? +

Delete a postal code target. 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_postal_code_target accept? +

delete_postal_code_target 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_postal_code_target? +

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

delete_postal_code_target 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_postal_code_target? +

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

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

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