replace_contract_document_file
Replace the file on a contract document
This record as markdown: /tools/adbutler/replace-contract-document-file.md
What replace_contract_document_file does on AdButler
AI agents use replace_contract_document_file 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 |
|---|---|---|---|
contract_id | number | Yes | Contract ID |
document_id | number | Yes | Document ID |
Parameters from the server's own tool schema.
Why replace_contract_document_file is rated Medium
This tool modifies existing data (a contract document file) in a reversible manner. While the action replaces a file, it is not permanently destructive since the previous version could theoretically be recovered or re-uploaded.
From the tool's definition Tool name 'replace_contract_document_file' and description 'Replace the file on a contract document' indicate modification of an existing document file within a contract management system.
Attacks that exploit this kind of access
The rule that runs replace_contract_document_file 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 replace_contract_document_file, this is the rule to start with:
replace_contract_document_file 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 replace_contract_document_file call is checked against it from then on.
Questions about replace_contract_document_file
Replace the file on a 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.
replace_contract_document_file accepts 2 parameters: contract_id, document_id. Required: contract_id, document_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 replace_contract_document_file: 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.
replace_contract_document_file 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 replace_contract_document_file 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 replace_contract_document_file. 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.
replace_contract_document_file 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