AI agents use create_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 |
|---|---|---|---|
name | string | Yes | Contract name |
rate | number | — | Contract rate (in account currency) |
end_at | string | — | Contract end date (YYYY-MM-DD) |
status | string | — | Contract status |
start_at | string | — | Contract start date (YYYY-MM-DD) |
advertiser | number | Yes | 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 creates a new contract, which is a Write operation—it creates data reversibly without deleting or destroying anything. Severity is medium because contracts in an ad management platform typically involve business commitments and financial implications, making misuse moderately impactful.
From the tool's definition Tool name 'create_contract' and description 'Create a new contract' indicate data creation. The sibling tools (archive_*, bulk_create_*, bulk_upload_*) show this server manages significant business entities (campaigns, zones, contracts, advertisers,…
Attacks that exploit this kind of access
Create a new 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.
create_contract accepts 8 parameters: name, rate, end_at, status, start_at, advertiser, description, payment_due_date. Required: name, advertiser. 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 create_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.
create_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 create_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 create_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.
create_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 →