update_contract_template
Update an existing contract template
This record as markdown: /tools/adbutler/update-contract-template.md
What update_contract_template does on AdButler
AI agents use update_contract_template 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 template ID |
name | string | — | Template name |
Parameters from the server's own tool schema.
Why update_contract_template is rated Medium
The tool creates or modifies contract template data without deleting it, fitting the Write category. Severity is medium because contract templates may be important business documents, but the modification is reversible and does not involve financial transactions, code execution, or irreversible deletion.
From the tool's definition Tool name contains 'update' and description states 'Update an existing contract template' – this modifies existing data reversibly.
Attacks that exploit this kind of access
The rule that runs update_contract_template safely
PolicyLayer is an MCP gateway: it sits between your AI agents and AdButler, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For update_contract_template, this is the rule to start with:
update_contract_template stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect AdButler, apply this rule, and every update_contract_template call is checked against it from then on.
Questions about update_contract_template
Update an existing contract template. 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_template accepts 2 parameters: id, name. 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_template: 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_template 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_template 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_template. 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_template 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.
More on AdButler, and thousands of servers like it.
This server
Across the catalogue