AI agents use update_contract 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 | Contract ID |
name | string | — | Contract name |
rate | number | — | Contract rate |
end_at | string | — | Contract end date (YYYY-MM-DD) |
status | string | — | Contract status |
start_at | string | — | Contract start date (YYYY-MM-DD) |
advertiser | number | — | Advertiser ID |
description | string | — | Contract description |
payment_due_date | string | — | Payment due date (YYYY-MM-DD) |
Parameters from the server's own tool schema.
This tool modifies contract data reversibly. It does not delete, execute code, or move money directly. However, because contracts may have financial implications in an advertising platform, and updates could affect contract terms, pricing, or obligations, this warrants medium severity.
From the tool's definition Tool name is 'update_contract' and description states 'Update an existing contract'. The verb 'update' indicates modification of existing data.
Attacks that exploit this kind of access
Update an existing contract. 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_contract accepts 9 parameters: id, name, rate, end_at, status, start_at, advertiser, description, payment_due_date. 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_contract: 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_contract 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_contract 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_contract. 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_contract 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 →