update_contract_document
Update an existing contract document
This record as markdown: /tools/adbutler/update-contract-document.md
What update_contract_document does on AdButler
AI agents use update_contract_document 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 | Document ID |
name | string | — | Document name |
contract_id | number | Yes | Contract ID |
Parameters from the server's own tool schema.
Why update_contract_document is rated Medium
The tool modifies contract documents reversibly—updates can typically be undone or versioned. This is a Write operation, not Execute (no code/command execution), Destructive (reversible), or Financial (no direct money movement, though contracts may have financial implications).
From the tool's definition Tool name 'update_contract_document' and description 'Update an existing contract document' indicate modification of existing data (Write category).
Attacks that exploit this kind of access
The rule that runs update_contract_document 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_document, this is the rule to start with:
update_contract_document 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_document call is checked against it from then on.
Questions about update_contract_document
Update an existing contract document. 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_document accepts 3 parameters: id, name, contract_id. Required: id, contract_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_document: 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_document 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_document 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_document. 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_document 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