AI agents use update_postal_code_target 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 | Postal code target ID |
label | string | — | Postal code target name |
inclusive | boolean | — | If true, inclusion target; if false, exclusion target |
locations | array | — | Array of locations grouped by country |
Parameters from the server's own tool schema.
This tool modifies campaign configuration (postal code targeting parameters) reversibly. It is a Write operation because it updates existing data without deletion. Severity is medium because misconfiguration of ad targeting could impact campaign performance and budget allocation, but does not involve irreversible deletion, code execution, or financial transactions.
From the tool's definition Tool name 'update_postal_code_target' and description 'Update an existing postal code target' indicate modification of existing data within AdButler campaign targeting rules.
Attacks that exploit this kind of access
Update an existing postal code target. 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.
update_postal_code_target accepts 4 parameters: id, label, inclusive, locations. 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 update_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.
update_postal_code_target is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the update_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.
Set action: deny in the PolicyLayer policy for update_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.
update_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.
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 →