replace_contract_document_file_from_template

WHAT IT DOES

What replace_contract_document_file_from_template does on AdButler

AI agents use replace_contract_document_file_from_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.

PARAMETERS

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 IT NEEDS A POLICY

Why replace_contract_document_file_from_template needs a policy

The tool modifies an existing contract document by replacing its file content from a template. This is a Write operation (reversible modification), not Read (no query), not Execute (no code/command execution), not Destructive (document not deleted, can be reverted), not Financial (no direct money movement).

From the tool's definition Tool name contains 'replace' and description states 'Replace a contract document file from a template', indicating modification of existing contract data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

replace_contract_document_file_from_template Rate-limited

replace_contract_document_file_from_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "replace_contract_document_file_from_template": {
      "limits": [
        {
          "counter": "replace_contract_document_file_from_template_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches AdButler, so you can run agents against it safely.

FAQ

Questions about replace_contract_document_file_from_template

What does the replace_contract_document_file_from_template tool do? +

Replace a contract document file from a 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.

What parameters does replace_contract_document_file_from_template accept? +

replace_contract_document_file_from_template 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.

How do I enforce a policy on replace_contract_document_file_from_template? +

Register the AdButler MCP server in PolicyLayer and add a rule for replace_contract_document_file_from_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.

What risk level is replace_contract_document_file_from_template? +

replace_contract_document_file_from_template is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit replace_contract_document_file_from_template? +

Yes. Add a rate_limit block to the replace_contract_document_file_from_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.

How do I block replace_contract_document_file_from_template completely? +

Set action: deny in the PolicyLayer policy for replace_contract_document_file_from_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.

What MCP server provides replace_contract_document_file_from_template? +

replace_contract_document_file_from_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.