AI agents use update_pmp_deal 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 | PMP deal ID |
name | string | — | PMP deal name |
bid_floor | number | — | Bid floor |
geo_target | number | — | Geo target ID |
audience_target | number | — | Audience target ID |
whitelist_seats | array | — | Seat IDs with access |
Parameters from the server's own tool schema.
This tool creates or modifies data reversibly (characteristic of Write category). Updating PMP deals affects ad campaign configurations, pricing terms, and inventory allocations but does not permanently delete data or execute arbitrary code. The 'high' severity reflects that misuse could alter critical advertising agreements and financial terms affecting campaign performance and revenue.
From the tool's definition Tool name 'update_pmp_deal' and description 'Update an existing PMP deal' indicate modification of programmatic media buying deal data. PMP (Private Marketplace) deals control ad inventory allocation and pricing agreements.
Attacks that exploit this kind of access
Update an existing PMP deal. 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_pmp_deal accepts 6 parameters: id, name, bid_floor, geo_target, audience_target, whitelist_seats. 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_pmp_deal: 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_pmp_deal 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_pmp_deal 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_pmp_deal. 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_pmp_deal 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 →